01-16-2016, 06:34 PM
Quote:The "destroyed" trigger is unreliable with 64-bit windows. Also if checked "Other" in Options -> Triggers -> Low level hooks.
Because then QM receives the notification asynchronously, often when the window is already destroyed, and therefore cannot get window name/class to compare.
When the macro runs, the window probably is destroyed in other cases too, therefore the handle is invalid.
To make the trigger reliable, QM would have to periodically get and cache name/class/etc of all windows, ahead of time, to be compared later when the window is destroyed. It would use much CPU... Or would need a 64-bit process running all the time. Nobody likes too see many processes in Task Manager.
Recommended workaround:
Create a function that runs when the window is created. Let it get window handle (int hwnd=TriggerWindow) and wait until the window is destroyed (wait 0 -WC hwnd)...