locoDog
Not a operational bug but I've spotted a conflict that may in the future need to be addressed.
I'm making a skin with 10 custom buttons per deck, (I use them as visuals for effects switched by the keyboard and in the end will have about 200 more) now to make sure I don't end up with buttons meant for others decks (when a user switches skin) in the wrong place I've done this.
i.e. in default
deck 1 buttons 1-4
d2 6-9
d3 11-14
d3 16-19
So to maintain the original user config I've given deck 1 buttons 1-4 & 21-26, etc
but the problem is there's a few skins that have additional custom buttons, and If you switch between them things get annoying
What I suggest is that the definition text of custom buttons includes the skin name query
if defaultskin? [button config] : If locoskin ? [a different config]
Certainly not a issue for 99.99% of cases now, but perhaps something to consider once things are stable (maybe in the future everything will be customisable & panelled,)
I'm making a skin with 10 custom buttons per deck, (I use them as visuals for effects switched by the keyboard and in the end will have about 200 more) now to make sure I don't end up with buttons meant for others decks (when a user switches skin) in the wrong place I've done this.
i.e. in default
deck 1 buttons 1-4
d2 6-9
d3 11-14
d3 16-19
So to maintain the original user config I've given deck 1 buttons 1-4 & 21-26, etc
but the problem is there's a few skins that have additional custom buttons, and If you switch between them things get annoying
What I suggest is that the definition text of custom buttons includes the skin name query
if defaultskin? [button config] : If locoskin ? [a different config]
Certainly not a issue for 99.99% of cases now, but perhaps something to consider once things are stable (maybe in the future everything will be customisable & panelled,)
Posted Fri 08 Aug 14 @ 6:45 pm
jah love 36
good idea!
Posted Fri 08 Aug 14 @ 6:59 pm