 Cody0248 1 discussion post
|
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
Sep 24, 2019
• #1
|
|
|
What application is it? Could you also send me a copy of the TrayStatus troubleshooting info?
Thanks! |
 DJS05 9 discussion posts
|
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 ?
May 6, 2021
• #3
|
|
|
@DJS05: I'm not quite sure what you mean. Is it that when the child windows open, NumLock gets disabled?
May 7, 2021
• #4
|
|
DJS05 9 discussion posts
|
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
• Attachment [protected]: Screenshot 2021-05-07 193045.jpg [304,969 bytes]
• Attachment [protected]: Screenshot 2021-05-07 193127.jpg [217,506 bytes]
May 7, 2021
• #5
|
|
DJS05 9 discussion posts
|
... sorry, did not recognize that the screen shot program deactivated the Numlock in the first image ... Should be active.
May 7, 2021
• #6
|
|
DJS05 9 discussion posts
|
... now with images as they should be without the screenshot tool.
• Attachment [protected]: Screenshot Strom-Eingabe.jpg [293,691 bytes]
• Attachment [protected]: Screenshot Strom.jpg [362,136 bytes]
May 7, 2021
• #7
|
|
|
In the Trigger rule, if you disable the "Revert Button State" option, does that make any difference?
May 10, 2021
• #8
|
|
DJS05 9 discussion posts
|
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.
May 10, 2021
• #9
|
|
DJS05 9 discussion posts
|
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.
• Attachment [protected]: Screenshot 2021-05-10 163035.jpg [252,688 bytes]
May 10, 2021
• #10
|
|
|
Ok, thanks for confirming! It seems to be treating the child window as a separate application and reverting the key state even though it shouldn't. I'll add this to our list to fix up for the next version
In the meantime, if you leave that "Revert button state" set to off, and add a second rule for "After No Match" to disable numlock, I think that will work around the issue for now. Thanks!
May 10, 2021
• #11
|
|
DJS05 9 discussion posts
|
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 • Attachment [protected]: Screenshot_German.jpg [61,211 bytes]
May 10, 2021
• #12
|
|
|
Just a quick update on this, we should have a new beta out tomorrow that will fix this up. I'll follow-up again when it's available to try out.
Thanks!
May 18, 2021
• #13
|
|
DJS05 9 discussion posts
|
Keith, thanks for your update. Waiting for the SW to come. Best regards, Jürgen
May 19, 2021
• #14
|
|
|
The beta is available now, could you try updating and let me know how it works out?
Thanks!
May 20, 2021
• #15
|
|
DJS05 9 discussion posts
|
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 • Attachment [protected]: TrayStatus Language.jpg [64,179 bytes]
May 20, 2021
• #16
|
|
|
Glad to hear it! I've fixed up that translation here and it will be included in the next version
May 25, 2021
• #17
|
| Was this helpful? | |
