I'm trying out a new style of mapping where effects modify several decks if a variable for that deck is on, and as a result the scripts are Very long
var "d1" ? var "d2" ? var "d3" ? var "d4" ? deck master effect_active : deck 1 effect_ active & deck 2 effect_active & deck 3 effect_active : deck 1 effect_active & deck 2 effect_active & var "d4" ? deck 4 effect_active : nothing : deck 1 effect_active & var "d3" ? deck 3 effect_active & var "d4" ? deck 4 effect_active : nothing : var "d4" ? deck 4 effect_active : nothing : var "d2" ? var "d3" ? var "d4" ? deck 2 effect_active & deck 3 effect_active & deck 4 effect_active : deck 2 effect_active & deck 3 effect_active : deck 2 effect_active & var"d4" ? deck 4 effect_active : nothing : var "d3" ? var "d4" ? [ABANDON SCRIPT] I thought I had it but it's gone
I've already confused myself, and this is not even taking account of the 6 'modes' I'll have.
So anyway if you could close off a query it would be much easier (I'll use ¬ to represent close query)
var "d1" ? deck 1 effect_active : nothing ¬ & var "d2" ? deck 2 effect_active : nothing ¬ & var "d3" ? deck 3 effect_active : nothing ¬ & var "d4" ? deck 4 effect_active : nothing
var "d1" ? var "d2" ? var "d3" ? var "d4" ? deck master effect_active : deck 1 effect_ active & deck 2 effect_active & deck 3 effect_active : deck 1 effect_active & deck 2 effect_active & var "d4" ? deck 4 effect_active : nothing : deck 1 effect_active & var "d3" ? deck 3 effect_active & var "d4" ? deck 4 effect_active : nothing : var "d4" ? deck 4 effect_active : nothing : var "d2" ? var "d3" ? var "d4" ? deck 2 effect_active & deck 3 effect_active & deck 4 effect_active : deck 2 effect_active & deck 3 effect_active : deck 2 effect_active & var"d4" ? deck 4 effect_active : nothing : var "d3" ? var "d4" ? [ABANDON SCRIPT] I thought I had it but it's gone
I've already confused myself, and this is not even taking account of the 6 'modes' I'll have.
So anyway if you could close off a query it would be much easier (I'll use ¬ to represent close query)
var "d1" ? deck 1 effect_active : nothing ¬ & var "d2" ? deck 2 effect_active : nothing ¬ & var "d3" ? deck 3 effect_active : nothing ¬ & var "d4" ? deck 4 effect_active : nothing
Posté Tue 01 Jul 14 @ 11:09 am
Any news ?
Posté Sun 25 Apr 21 @ 6:07 am
Locodog - I see that this is a very old post but it looks to me like you were trying to implement a kind of Serato style Deck Fx banks assignation.....
I've been thinking of toying around with producing a mapping for this for myself recently for fun..... and I can see that while probably possible the scripting could quickly become like a mapping bowl of spaghetti...... did you ever get anywhere with it or did you give up?
I've been thinking of toying around with producing a mapping for this for myself recently for fun..... and I can see that while probably possible the scripting could quickly become like a mapping bowl of spaghetti...... did you ever get anywhere with it or did you give up?
Posté Sun 25 Apr 21 @ 2:33 pm
I abandoned the idea :( I bought more buttons :)
Posté Sun 25 Apr 21 @ 2:45 pm
I just reactivated it because it's the common request about parenthesis to group commands ^^
(var "d1" ? deck 1 effect_active : nothing) & (var "d2" ? deck 2 effect_active : nothing) & (var "d3" ? deck 3 effect_active : nothing) & var "d4" ? deck 4 effect_active : nothing
but yes, the extra "button" hack is the only current way (with its set of issues)
(var "d1" ? deck 1 effect_active : nothing) & (var "d2" ? deck 2 effect_active : nothing) & (var "d3" ? deck 3 effect_active : nothing) & var "d4" ? deck 4 effect_active : nothing
but yes, the extra "button" hack is the only current way (with its set of issues)
Posté Sun 25 Apr 21 @ 11:19 pm
Nicotux wrote :
parenthesis to group commands
+1
Posté Sun 25 Apr 21 @ 11:52 pm
what is strange is ... filter folder script already implement this for years
(even new combo boxes prevent their use and limits the possibilities)
(even new combo boxes prevent their use and limits the possibilities)
Posté Mon 26 Apr 21 @ 12:12 am