Allow separate bindings for wheel up/down

[eugenesvk]

For example, I'd like to bind Window list to wheel UP and Stacked window list to wheel down
But currently only mostly "paired" actions are allowed to be bound to mouse wheels

[RamonUnch]

AltSnap1.66test9_x64.zip

Try with this version.
Add in the [Input] section of the .ini

Scroll=Action on scroll Down
ScrollUp=Action on scroll Up.

If no action is specified for ScrollUp, it will be the same than for scroll down.

It is an .ini only option for now, I will maybe think about config integration later.

[Ichisich]

Comes in handy.
Tested it with ScrollUpM and ScrollUpR.

[eugenesvk]

Thanks for adding the feature! After some testing there are 2 issues with it when I bind lists to it:

• repeating the command toggles instead of leaving the list on. And with a scroll it's especially easy to scroll by 2-3-4-... notches instead of just 1. Is it possible to add AltTabList/StackList NoToggle commands where you can only dismiss the list with Escape or by selecting an app from the list, but a second invocation of the same command does nothing (well, except updating the list if it's changed in between, then it's fine to flash the list, but still not close it)
• I see that for some reason there are also CtrlDown/Up events sent when I run the list command. Is it possible to add an option to disable them since they interfere with my other keybindings via AHK?

I have DragSendsAltCtrl=0 which is the only config I've found to be related to that, but maybe I've missed something else.

[RamonUnch]

Maybe use EndSendKey=FF instead of 11.

this key is used after you pressed Alt and an action occurred to avoid selecting the menu.

I do not see the problem of having the menu blink if you wheel more than one notch, is that the issue? I am not sure I understand.

[eugenesvk]

The blinking is one issue (it shouldn't blink if the content hasn't changed), the second issue is that the menu disappears altogether. Although I was wrong that it happens on 2 notches, it happens when you scroll too fast (think even 3-notch-length fast scroll can trigger it, though not certain, but 4-5 fast scroll events definitely trigger the hiding, slow 4-5 scroll events just do the blinking)

I have Win key as accelerator, so it shouldn't mask the Alt key at all as there is no alt key!

But I've also tried FF and 00, but still got artificial Ctrl events, so this EndSendKey has no effect

[RamonUnch]

Give me your ini file, this is strange

[RamonUnch]

I see OK, this only happens when yo use the WinKey because otherwise the menu won't get selected.
I will see If maybe another key can be sent in this case too.

[eugenesvk]

config

I've remapped windows start menu (if you mean this menu) to another combination Winkey+Shift, so wouldn't need to mask Winkey at all

Though strangely enough, sometimes the start menu still pops up even though I don't see Shift in the AHK keyboard log, not sure what's going on here, but hopefully once I can disable any Up masking key events for Winkey trigger it will disappear automagically.

[RamonUnch]

AltSnap1.66test10_x64.zip

The above version should not send control for the menu popup.

It seems it is not needed to send ctrl for a menu popup. It is required in some cases when AltSnap wants to focus a window from another process. Even like this it is not reliable. Windows never lets you fully control which windows is in the foreground.

[eugenesvk]

Thanks for the fix!
EndSendKey are still being sent, not sure if that's intentional for Win-key mousewheel commands, but at least now EndSendKey=00 works, no extra keys are being sent

So curently only 2 issues remain:

• (visual annoyance) flashing on continuous commands (easy with a mouse wheel)
• disappearance of the menu when you scroll too fast

[RamonUnch]

Unfortunately there is no way to add entries to a menu once it is opened without destroying/recreating.

There were two things:

• A Control key is sent when a window is focused by AltSnap (it is needed for the focusing to work more reliably but is no longer done for the Menu creation).

• Also when the HotKey has been pressed AND an action occurred it means that the user did not actually want to press the hotkey by itself, thus before releasing the hotkey AltSnap will send the EndSendKey. Otherwise you would have the Start menu pop up wen you Win+Click.

In your specific case you do not use WinKey for the Start menu but for all other users it would be unusable without the EndSendKey.
Given that AltSnap cannot know if your rebound random keys from the outside the parameters have to be manually changed.

[eugenesvk]

Unfortunately there is no way to add entries to a menu once it is opened without destroying/recreating.

That's fine, I only mean situations when nothing changed, this happens when you scroll by 2-3 clicks instead of 1 right away (common with "free-scrolling" wheel mode). So all that is needed is not to destroy/recreate the already functional and correct list (store the old list, compare the new to the old, and if they are the same, don't destroy the extisting window)