[Bug] Pulse parameter executes like a momentary #33
Description
Issue Description
when clicking a pulse type parameter, instead of acting like a pulse does in TD (0, 1, 0 in a single frame), it acts like a momentary, and will constantly execute, making a parexec continuoulsy execute until released instead of executing a single time, which really borks things that should only happen once
Steps to Reproduce
naive example:
create a test case with a parexec and pulse. add a textTOP mapped to val of a constantCHOP, and set the onPulse of the exec to do something like increment a constantCHOPs value.
onPulse
if par.name == "Pulse":
op('constant1').par.const0value = int(op('constant1').par.const0value) + 1
you'll see that this value increments forever while held down, instead of just happening once per click. This wreaks havoc on any execs relying on executing a single time.
A workaround is instead using a momentary and not a pulse, and setting the exec up so that onValueChange
if par.val == 0:
do a thing
this gets me the functionality i want in resolume, but then breaks behavior in TD for the same things and causes a lot of manual rewriting in order to make things work.
My guess is that because pulse is a TD specific par style, you're trying to replicate it somehow, but it isn't quite getting functional parity. My recommendation is in your implementation to enforce only a single execution of this, maybe only on release if that's easy
Log File Location (Paste Path or URL)
none
Paste Resolume Log File
none
Upload TouchDesigner (.toe) File
https://drive.google.com/file/d/1Ba6IOpuVelztoCLJI_xbSRtEVPd91Q2r/view?usp=sharing
Plugin Version
1.15
Windows Version
Windows 11
Resolume Version
7.23.2
Plugin Version Confirmation
- I confirm that I am using the latest version of the plugin.