Preset Strategy
dtucker
Posts: 7
What is the general strategy for savings presets (could be channel presets, camera presets, or something else).
In general I see "push to recall a preset", and "hold to save a preset".
However, if you are trying to save a preset, the PUSH event will fire before the HOLD event, meaning any time you try and save a preset, the previous preset will be recalled and then resaved. In short, the problem is both PUSH and HOLD fire, not PUSH or HOLD.
I can think of several messy ways to solve this problem, such as setting a timer on PUSH and reading it on RELEASE to see if they pushed or held. But I figure there may be a more elegant solution.
How do you all generally go about handling presets?
In general I see "push to recall a preset", and "hold to save a preset".
However, if you are trying to save a preset, the PUSH event will fire before the HOLD event, meaning any time you try and save a preset, the previous preset will be recalled and then resaved. In short, the problem is both PUSH and HOLD fire, not PUSH or HOLD.
I can think of several messy ways to solve this problem, such as setting a timer on PUSH and reading it on RELEASE to see if they pushed or held. But I figure there may be a more elegant solution.
How do you all generally go about handling presets?
0
Comments
On HOLD:
- the ButtonHold variable is set to True.
- Execute Code for a HOLD Event
On RELEASE:
- If ButtonHold is False
- Execute Code for a RELEASE Event that would otherwise be done in a PUSH Event
- the ButtonHold variable is set to False.
Paul