synthet1c
nah 'cue jump' is only a variable, so you should be able to map for it
var 'cue_jump' 0 ? action if tue : action if false
but you could also leave it if the end, because if all other variables are false this must be true
var 'cue_jump' 1' ? goto_cue 2 : var 'cue_jump' 2 ? goto_cue 3 : var 'cue_jump' 3 ? goto_cue 4 : var 'cue_jump' 4 ? goto_cue 5 : var 'cue_jump' 5 ? goto_cue 6 : goto_cue 1
var 'cue_jump' 0 ? action if tue : action if false
but you could also leave it if the end, because if all other variables are false this must be true
var 'cue_jump' 1' ? goto_cue 2 : var 'cue_jump' 2 ? goto_cue 3 : var 'cue_jump' 3 ? goto_cue 4 : var 'cue_jump' 4 ? goto_cue 5 : var 'cue_jump' 5 ? goto_cue 6 : goto_cue 1
Posted Mon 26 Sep 11 @ 4:54 pm
ClayDJ
Here is a bit more info:
You may have answered my question in your previous post (I have not check it yet), please let me know if it is still valid after this info;
Here is my current map (excluding pos, size width, etc.).
(I have only listed strings for two cues to keep things simple).
These strings allow the color to change on my cue buttons as I cycle through them using the controller knob or clicking on the UI . This lets me visually see that a 'green' cue button is an active cue while all the remaining cue buttons remain 'red' (inactive cues).
Cue button panel id:
<panel id="leftcue1on" group="leftcues1" visible="deck 1 var 'cue_jump' 0 ? true : false">
<panel id="leftcue1off" group="leftcues1" visible="deck 1 var 'cue_jump' 0 ? false : true">
<panel id="leftcue2on" group="leftcues2" visible="deck 1 var 'cue_jump' 1 ? true : false">
<panel id="leftcue2off" group="leftcues2" visible="deck 1 var 'cue_jump' 1 ? false : true">
Cue Button Panel:
<button panel="leftcue1on" action="deck 1 hot_cue 1 & deck 1 set 'cue_jump' 0">
<button panel="leftcue1off" action="deck 1 hot cue 1 & deck 1 set 'cue_jump' 0">
<button panel="leftcue2on" action="deck 1 hot cue 2 & deck 1 set 'cue_jump' 1">
<button panel="leftcue2off" action="deck 1 hot cue 2 & deck 1 set 'cue_jump' 1">
The above strings work great when cycling the cues including the proper colors once combined with the correct pos, size weight, etc XML lines (not noted here).
The problem is: Notice in the cue button panel syntax: "& deck 1 set 'cue_jump'" statement?
As far as I know, this statement must be placed there in order for proper cue/color cycling to take place.
Due to the "deck 1 set 'cue_jump' 0" statement, every time I select a cue, I am also setting the cue point (which I do not want to happen).
What should happen is: when a cue is selected, play should start from that cue point (no cue point setting).
In the above strings: if the cue strings were cue 1 = cue 1 then there would be no issue, but since I have to set each cue to the next lower cue number is where it screws things up.
Is there a way to set this cue 0/cue 1 action elsewhere maybe as a skin default when the skin loads (I need it removed from the button panel statements)?
Hopefully I explained things ok.
Thanks again for your help
Clay
You may have answered my question in your previous post (I have not check it yet), please let me know if it is still valid after this info;
Here is my current map (excluding pos, size width, etc.).
(I have only listed strings for two cues to keep things simple).
These strings allow the color to change on my cue buttons as I cycle through them using the controller knob or clicking on the UI . This lets me visually see that a 'green' cue button is an active cue while all the remaining cue buttons remain 'red' (inactive cues).
Cue button panel id:
<panel id="leftcue1on" group="leftcues1" visible="deck 1 var 'cue_jump' 0 ? true : false">
<panel id="leftcue1off" group="leftcues1" visible="deck 1 var 'cue_jump' 0 ? false : true">
<panel id="leftcue2on" group="leftcues2" visible="deck 1 var 'cue_jump' 1 ? true : false">
<panel id="leftcue2off" group="leftcues2" visible="deck 1 var 'cue_jump' 1 ? false : true">
Cue Button Panel:
<button panel="leftcue1on" action="deck 1 hot_cue 1 & deck 1 set 'cue_jump' 0">
<button panel="leftcue1off" action="deck 1 hot cue 1 & deck 1 set 'cue_jump' 0">
<button panel="leftcue2on" action="deck 1 hot cue 2 & deck 1 set 'cue_jump' 1">
<button panel="leftcue2off" action="deck 1 hot cue 2 & deck 1 set 'cue_jump' 1">
The above strings work great when cycling the cues including the proper colors once combined with the correct pos, size weight, etc XML lines (not noted here).
The problem is: Notice in the cue button panel syntax: "& deck 1 set 'cue_jump'" statement?
As far as I know, this statement must be placed there in order for proper cue/color cycling to take place.
Due to the "deck 1 set 'cue_jump' 0" statement, every time I select a cue, I am also setting the cue point (which I do not want to happen).
What should happen is: when a cue is selected, play should start from that cue point (no cue point setting).
In the above strings: if the cue strings were cue 1 = cue 1 then there would be no issue, but since I have to set each cue to the next lower cue number is where it screws things up.
Is there a way to set this cue 0/cue 1 action elsewhere maybe as a skin default when the skin loads (I need it removed from the button panel statements)?
Hopefully I explained things ok.
Thanks again for your help
Clay
Posted Mon 26 Sep 11 @ 6:01 pm