- Edited
too complicated to post. Input events are polled in the Main node script.
I just put a print statement under the Input.is_action_just_pressed statement and many times it doesn't print anything.
One weird thing thing I've found:
-I'm using the command to call a function in a child node. Normally the _process for the node is just PASSing but the click initiates a sequence of _process calls to implement moving a rectangle around (popup text box).
While that process is running, the input event is captured every single time. It's weird because this seems backwards since there is nothing to cause a lag.
Not using timers, just math with the _process delta value.
edit: just discovered another bit of behavior (I feel a hack coming on lol)
If I move the mouse just a smidgen it recognizes the click every time. Reclicking in the same spot is where I get the weird behavior. I'm not using any move-movement commands. Perhaps I can flush something?