Page 2 of 2

Re: Comments from a console on Tour

Posted: Sun Sep 14, 2008 8:56 am
by RobertBell
Shift+Go is ASSERT current cue (as you described above Rob)

We've just added a softkey to the CUE command called RUN NEXT which is the old 500 LOAD CUE on playback (changes next GO). We could add a shifted version of this softkey called Assert Next. Thoughts on need for that?

Re: Comments from a console on Tour

Posted: Sun Sep 14, 2008 6:47 pm
by JohnGrimshaw
Assert Next would be "go" wouldn't it?

Re: Comments from a console on Tour

Posted: Sun Sep 14, 2008 8:05 pm
by RobertBell
No. It would be GOTO in Cue Time

GO does not assert levels that are tracking. GOTOS (and ASSERTS) give you full stage state (tracking levels and hard levels for the next cue).

Re: Comments from a console on Tour

Posted: Sun Sep 14, 2008 9:02 pm
by JohnGrimshaw
Ah - then yes, that would be useful. Reminds me that I would still like to see function descriptions appear in a discrete panel as they are used.

No, not "Clippy" as discussed in the Beta section here:
viewtopic.php?f=15&t=990&hilit=+clippy#p4525
Hooky-1.jpg
Hooky-1.jpg (11.39 KiB) Viewed 1005 times

Re: Comments from a console on Tour

Posted: Mon Sep 15, 2008 5:59 am
by gooze
Assert a cue, could we please do that by typing:
[CUE][#][GO]?

Re: Comments from a console on Tour

Posted: Mon Sep 15, 2008 7:48 am
by RobertBell
Being that it's Only Code you would think that the answer could be YES. I've been told many times over the years that the answer is 'no' for some technical reason I still can't get my head around.

Re: Comments from a console on Tour

Posted: Mon Sep 15, 2008 5:46 pm
by TaineGilliam
If "Clampy" there shows up dancing across my screen I just may loose it. :)

For all you Genius folk, I would hope [Cue] # [Go] would Go on the cue and [Cue] # [Goto] would be the assert cue syntax.

Much like the difference between [Goto] # [Enter] (asserts) and [Goto] # [S8-Move Fade] [Enter] (does not assert) for us LP guys, right?

Taine