Linking the proposed behaviour to the zoom hotkeys as opposed to directly to the mousewheel handler is by far the easier approach to take here. It's a few lines of code and it works perfectly.

Attempting to hard-code it to the wheel would be a lot more of a bug-prone effort. The wheel can currently have any hotkey action linked to it, so we'd have to find a way to bypass that action (from a place of not necessarily knowing what the action is) as well as implementing the new framestepping behaviour and ensuring that other mousewheel event handling isn't affected. Not trivial, and tbh not worth the effort.

Let's add the framestepping behaviour as a modifier-accessible action of zoom in/out, then. I imagine that the vast majority of users keep zoom in/out linked to the mousewheel anyway. The framestepping, then, is a nice added bonus.

So, ensuring that zoom in/out remains linked to the mousewheel, we have:

Wheel only = zoom in/out
Ctrl+Wheel = step +1/-1
Shift+Wheel = step +10/-10
Alt+Wheel = step +100/-100

Let's give this a try in CE 1.1 and see what we think.

Implemented in commit 2b75880.

stoners of a different kind

using an industrial megacrane what would happen if you drop vexle one meter off the ground
(If your wondering who vexle is watch lemming race tests)

Little progress update: scrapped 1 level, made 6 more for a total of 19 out of 30!

Here's a few previews:


"Follow me!" / "Wait for me!"


"The Lemming Hair Dryer"


"Freezer Burn"

Here's hoping I don't run out of ideas anytime soon

I will be on a buisness trip until thursday evening, so it could be that the new rounds only starts on friday.

I see the trouble coming from having the modifier keys used only for modifiers too. I think it'd break the habits of many player.
So yeah maybe the latter solution by WillLem where you set a default frameskip on CTRL+wheel up or down is the best.

Personnaly I'd prefer the frame skip to be +/1 frame on the CTRL+wheel, I like to have precise frame step at hand and can use the keyboard if I want faster skips. But while we're at it, why not :

* wheel only = zoom as usual
* CRTL+wheel = +/- 1 frame skip
* SHIFT+wheel = +/- 10 frames skip

It's in the title.  I always uncheck "post redirection topic" and I imagine that other mods do the same (since we don't see a lot of redirection topics, but we do see a lot of topics being moved). Maybe the check should be un-ticked by default?

Quote from: Simon on January 20, 2026, 07:56:00 AMDoes the trouble arise from the design of the keybinding dialog?

No. I don't think the program is able to distinguish between "keydown" and "keyheld", at least not currently.

Wouldn't "keyheld" necessarily have to fire "keydown" anyway? I could be incorrect in this assumption.

Anyways, what would be possible without changing or adding any existing modifier key logic would be to simply implement "Ctrl + zoom hotkey in/out = frame step +1/-1." I'm happy to add that. Most users are likely to leave zoom in/out linked to the mousewheel, and it seems a good idea to also be able to framestep like this by default.

A thought occurs though. Using the mousewheel to framestep is a good idea, but maybe the increments should be slightly larger than 1. I'd suggest somewhere between 5 and 10 as a good alternative. It makes movement forwards & backwards more what you'd expect from mousewheel use.

You don't have to remove single keybindings for this. The program should be able to fire event A on LCtrl-down, and later fire event B on ((LCtrl-held or RCtrl-held) + another-key-down).

LShift-down and LCtrl-down are handy in a left-hand layout.

Does the trouble arise from the design of the keybinding dialog?

-- Simon

Quote from: Guigui on January 17, 2026, 02:08:32 AM* CTRL + mousewheel up = chosen number of frames step forward
* CTRL + mousewheel down = chosen number of frames step backward

Hm. I agree, but this would mean treating the modifier keys only as modifiers. They could no longer be used on their own as single-fire key events.

I'm pretty sure a hack exists where you can use a modifier with itself (so, Ctrl+Ctrl) to get essentially the same behaviour as a single keypress, but I wonder if the key has to be held for a certain amount of time for that to work.

So, would anybody mind this being changed? Allow the modifiers to be used as modifiers, but no longer as hotkeys by themselves?