Cuelist action when un-pausing

[kproth]

I noticed a cuelist behavior while testing another change that doesn't seem right - but maybe it's by design?

Reference the attached workspace. It has a cuelist pointed to a chaser with 6 steps, each having a different scene, and all of the steps have infinite hold times.

If you:

• Start the cuelist
• Click the Pause button
• Click the Next arrow button twice
• Click the Pause button to unpause

At this point, the 3rd step is selected in the cuelist widget, but the 1st step's scene is still active. I thought maybe at this point the 3rd step's scene should become active, but I wasn't really sure.

If you then

• Click the Next arrow button

At this point, the 2nd step gets selected (presumably because step 2 was the "next step" at the time I paused the cuelist), and the 2nd step's scene goes active. I thought the 4th step and scene would go active at this point instead.

If the observations above are expected, then perhaps the oddity is that the next and previous buttons seem to still work while the chaser is paused?

Note 1 - it appears I get more or less similar behavior if I change the chaser's steps to have a 2 second hold time instead of infinite -- it resumes playback from the step it was on when I clicked the pause button, i.e. it goes to the 2nd step after un-pausing, not the 4th.

Note 2 - v4 has similar behavior, but I didn't want to post the same thing twice...

[giacomo]

glad to see that someone else has reported it, I find it misleading and it's a pity for v5:
http://qlcplus.org/forum/viewtopic.php?t=15762
A Good New Year

[MichelSliepenbeek]

This is not typical for V5, in V4 it works the same.

To me this makes sense: if you Pause a function and then UnPause it, you would expect it to continu where it was Paused.

If you:

• Start the cuelist

• Click the Pause button

• Click the Next arrow button twice

• Click the Start/Stop Button twice

you will get the expected result, the 3rd step will become active.


I have problems with calling this "misleading", maybe it is better to use "confusing (for some of us)".

[kproth]

Good point that a stop/start could be used to restart at the scene selected by next button while paused. But to make that work if it’s an intentional choice, you have to stop briefly, so you might as well stop then move then restart.

I’d suggest that next/previous buttons should be disabled while the cuelist is paused. Or, perhaps preferably, unpausing after changing the selection should transition to the new selection — which would allow you to pause, move to a desired new step and transition to it, all without stopping the lights.

[MichelSliepenbeek]

There is already a "drop down selection box" for "Behavior of the Next/Previous buttons when the chaser is not active: " in the Cue List Widget.
You could add a second "drop down selection box" for "Behavior of the Next/Previous buttons when the chaser is paused: ".