tigrotto wrote: ↑Mon Jul 24, 2017 5:47 pm
Hi!
I was testing @CameMode command before using it in my script and I think I found a bug...
When I'm holding and edge and type came(tested with @Edge(LongHold) and @EdgeHold(time) commands) the program, instead of moving to the specified line, wait until the holding time is over and THEN moves to the specified line
Never used the came mode but, according to the command description, it is working as intended, it is not a bug.
@camemode()'s only function is to move you to that specified part of the script when you write one of the trigger phrases (basically it is a "shortcut" version of @CustomMode() with fixed trigger phrases).
But if you put it togheter with a @holdedge then, until the edge hold timer has not passed, the program will not move on, thus the @camemode will not activate.
Sorry but you can't use it that way....the only way i can think about you obtaining what you want to obtain is to "simulate" a hold the edge like this:
@NullResponse @CameMode(goTo,came)
(edgeLoop)
edge now @Edge @SetDate[holdTimer, xx seconds]
(holdLoop)
@NullResponse @CheckDate(holdTimer)
#HoldTheEdge @Goto(holdLoop)
(holdTimer)
#LetTheEdgeFade @Wait(10) @Goto(edgeLoop)
(came)
You came!
@EndTease
@End
This way you activate the camemode, then make him edge, then when he is on edge you "fake" the hold the edge by looping the holdLoop until the holdTimer date has passed (which determines how long the holding will last).
If you trigger the came mode you should move to the came part and be done with it, if you don't, when the hold timer is passed, you move to the holdTimer subpart where you tell him to let the edge fade, wait for the timer and then move back to the edge loop and start it all over again.
I didn't test it but i think it should work
P.s: i've seen this error in your scripts (and in many other that have been used in other personalities) but, NEVER use @NullResponse @End (@EndTease), just use @End/EndTease.
There is no need to @Nullresponse end commands and, actually, it bugs them and get them ignored (at least so it was some versions ago, i don't remember if we fixed it but, in any case, just dont nullresponse them to be sure).