'Focused window' trigger gets triggered upon group activation


Here's a macro, with a Focused Window Trigger (The focused window title changes), that gets triggered immediately whenever I activate the macro group. To me this does not seem like the expected behaviour. But is this a feature or a bug?

My desired behaviour would be for the macro first being triggered upon first window changing after the macro group is activated. Like how the behaviour is when using Application Trigger (Any Application Activates) for a macro in a similarly set macro group.

Macro with Focused Window Title Changes trigger.kmmacros (1.7 KB)

That's really strange—I wouldn't think it should, but it definitely triggers on group activation. I displayed the front window title in the macro, and it represented what I was seeing as the (unchanged) frontmost window. @peternlewis will probably have to chime in here...


1 Like

Thank you for checking it out, and for confirming that it is not only for me that something strange is going on here. Curious to hear what Peter will make of these observations

I'll look in to it.

1 Like

This should be resolved for the next version.


Just a note. This change that was delivered in 11.0.3 forces me to split macro group that is dedicated to one browser web page into two parts. The one is always active, and another is being activated when the browser title contains some string.

Is there a macro trigger that runs a specific macro when its group was activated?

I would like to instantly run this one:
Page handlers. Search.kmmacros (4.0 KB)
when its macro group is being activated. This would allow me to completely switch from using "Available when a focused window title contains" condition to the "URL-Dependent Macro Enable/Disable" approach described here.

I do not believe there is (hopefully I will be proven wrong though), but I have also been thinking that a trigger like this would make allot of sense and oftentimes be very useful