Build 19: Active window tracking

[Freddie]

(about numlock example)

cool so maybe add checkbox to the dialog "with pass thru" option ?

Unless somebody thinks of something better.

that or automagically treat the checked "when numlock is on" and nothing in the top (keyed in) section as meaning that you should just look at the key status but not consume it ?

"When numlock is on" is a state, not an event. Only an event can trigger a hotkey. You have to do something (press a key) to make something happen. Which key do you press? That's what the top section is for.

(as I assume that if I say for instance "A" and numlock on; you won't touch / do anything with numlock on/off transitions)

I'm not sure I understand. Are you saying you define the trigger NumLockOn A?

That means, "If I press A while NumLock is on, Mojo should do the action."

There's no way to infer anything about passing from that trigger. Two people might define hotkeys with that same trigger. The first person might want A to pass, and the second might want the opposite.

(about mojo getting raised when mouse is on another screen)
any chance to make that invisible window independant from mojo's other windows so only the invisible one gets raised by the OS (if it's not possible to make it not do that at all)

I'm looking at the source code and it looks like the invisible window isn't even a factor. I'm not sure why this is happening.

I'll add apply in the feature requests in case you forget but for bugs do you need something to track them?

I think probably it would be better if I track bugs myself because users have no way to know whether something is a bug or unfinished work.

If you include unfinished work in the bug list you would immediately have dozens or maybe hundreds of items and it would only make the program look bad.