If you use pauses you create a Sequence and a Sequence is will normally be executed completely. It's actually intended to use Hold Zone if you want the assignment to stop when you release the button, so like that:
Code: Select all
;--- Xpadder Profile Data ---
DataType=Profile
Version=2012.12.31
Set1Stick1UpSlots=Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.50s,Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.10s,Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.10s,Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.10s,Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.10s,Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.10s,Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.10s,Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.10s,Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.10s,Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.10s,Arrow Up,HOLD ZONE 0.10s,HOLD ZONE 0.10s,Arrow Up
But this is a not really comfortable way to create a really long assignment. So you can stop the execution of a Sequence when releasing the button with a Release Zone assignment like that:
Code: Select all
;--- Xpadder Profile Data ---
DataType=Profile
Version=2012.12.31
Set1Stick1DownSlots=RELEASE ZONE 0.01s,PAUSE 0.01s,HOLD ZONE 0.01s,Arrow Down,PAUSE 0.50s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down,PAUSE 0.10s,Arrow Down
Both solutions before have the problem that the are only working for a limited time. Alternatively using Sets would also be possible if the assignment is hindering Xpadder from returning to Set1 while the sick direction is still held. With the
you should also not have the problem that the set selectors are causing trouble for each other. But on the other you don't have the possibility to only tap a stick direction (so only one key press), Xpadder would still change the set and you would be stuck there until pressing this stick direction again.
Still the only perfect solution would be a turbo function with a delay until it gets active.