09-05-2018, 06:53 AM
This helps, but the question is when it should be autorun?
If I set it up to start with Windows, the browser (or whatever target app) that launches after QM overrides the shortcut handler
I need the triggers should be re-registered always when the target application is launched and finishes registration of own shortcuts.
That should generally apply on any application where QM is invoked by keyboard shortcut.
On the second side I don't wish QM continually evaluated all processes (obviously it eats system resources)
If I set it up to start with Windows, the browser (or whatever target app) that launches after QM overrides the shortcut handler
I need the triggers should be re-registered always when the target application is launched and finishes registration of own shortcuts.
That should generally apply on any application where QM is invoked by keyboard shortcut.
On the second side I don't wish QM continually evaluated all processes (obviously it eats system resources)