I have a program whose window will not activate the trigger. I used the crosshairs in the Process Filename dialogue to select the path for this program, however, the trigger doesn't seem to activate when I click into the window. It's as if TrayStatus doesn't see tha the focus has changed to that window. What can I do?

Thank you, Cody

Similar problem: I activated a trigger for a window title "Strom" (without the quotes). That works fine for triggering the numlock. But this program has two child windows called "Strom : Eingabe" and "Strom Grafik". Both reset the numlock. When closing those application modal windows to go back to the main window numlock comes up again. Trigger rule is Window Text : Strom, Caps Lock : No change, Num Lock : Enable, Scroll Lock : No change, Revert button state : yes. No other rule defined, version is Traystatus Pro 4.5. Any idea ?

Keith, thanks for your reply. Yes, you have got it right, starting the main program "Strom" activates Numlock, starting the child window "Strom : Eingabe" deactivates Numlock. Closing the child window and by that going back to the main window activates numlock again. See attached screen shots. Best regards, Jürgen

... sorry, did not recognize that the screen shot program deactivated the Numlock in the first image ... Should be active.

... now with images as they should be without the screenshot tool.

Yes, it does. Starting "Strom" activates Numlock, going to the child windows (Strom Grafik or Strom : Eingabe) leaves Numlock on. When I go back to the main window Numlock stays on. When I terminate the main program/window "Strom" Numlock also stays on. So this helps in the child windows but not after complete termination when Numlock should be off.

Keith, don't know if this may be a hint for you. Looking at the task bar i saw that the "Strom" windows only show one entry "Strom". The new window "Strom : Eingabe" does not appear. I have set the task bar not to group windows as you can see from the Explorer entries.

Dear Keith, thanks a lot. If I may help for testing please let me know.

By the way, I tested with the "Trigger Type : No Match". That did not really work If I start "Strom", Numlock is on and if I end "Strom" Numlock is off. But if I start the "Numlock : Eingabe" child window, Numlock is also off and goes on again if I close that window, going back to the main window "Strom".

Another small thing is the German translation of the trigger configuration (see attached screen shot). The selection box of "Trigger Type" in both cases says "Nach keinem Treffer" which is "After no Match". So the first topic should read like "Bei einem Treffer".

Best regards,
Jürgen

Keith, thanks for your update. Waiting for the SW to come. Best regards, Jürgen

Keith, thanks a lot. I tested it with subwindows and even sub-subwindows all carrying "Strom" in their title. I set the trigger topic "Revert Button State" to on again. And - it worked all fine !!! NumLock stayed on during all (sub-)windows and turned off after quitting the main program.

Only the German translation of the trigger type still needs some correction, as mentioned somewhere above.

So thanks again for the quick fix and best regards from Germany (Lake Constance),
Jürgen