Hi,
2025.32820, win/mackeyboardinDAT always fires events, even while entering text in the editor window, textCOMP, and so on. There is no practical way to determine whether the user is entering text or triggering a shortcut.
Cheers,
Alex
If you want to filter on which panel it triggers, you need to use the panel parameter, see Keyboard IN DAT documentation. Drag any Panel COMP to that parameter, and now events will only be fired when any of the listed panels has focus.
See Help→Operator Snippets→Keyboard IN DAT for a practical example which shows exactly that 
The bug is:
According to the wiki: “…get key press events… Exception: while entering text in the editor window. “
This is the practically correct behavior.
The actual behavior is: key press events are always fired, and there is no workaround at all.
The practical case:
Define hotkeys for running your custom scripts globally. For example, Shift+D will accidentally run your script when you type D in a textDAT or textCOMP.
thanks for the example!
hmm I’m not sure about meaning of this line in docs “Exception: while entering text in the editor window” as that is quite broad and could mean a lot of things. And I agree that should be looked at as I don’t see that functionality at all.
One workaround for your case is to drag a top parent Container in your app to the panel parameter of Keyboard in DAT. That way the shortcuts only trigger when that comp has focus and not while you are editing Text DATs etc. Or another workaround is to enable that it only triggers in perform mode, that’s what I always do.
Hi @letsius and @nettoyeur
I guess the wiki is a bit ambiguous here:
whether they are control panels, Perform Mode or the network editor window. Exceptions: while entering text in the editor window.
We’ll look into the current behavior and I’ll add an RFE for more granular control over what keystrokes should be logged.
cheers
Markus
1 Like