- Jul
- 576
- 10
So, I’m learning the “on” stuff a bit more, and I hit a situation where I guess... I found a need to request a new “on” type?
So we have these “mouse-based” ons:
ON DBLCLICK [command]
ON LBUTTON [command]
ON MBUTTON [command]
ON RBUTTON [command]
These are great. I don’t even really know how to use them, but I’m excited they exist.
I’m in a situation where I want to respond to the text size being increased. Which is, specifically for me, Ctrl-MouseWheelUp / Ctrl-MouseWheelDown.
It’s another mouse-based event, but there’s no corresponding “on” handler for it.
(It turns out if you lock certain rows to be non-scrollable, your cursor can either be in the normal part, or the locked part -- typically a 1–3 line statusbar. You can end up getting trapped inside the status bar if and only if the text size is changed without re-segregating the status bar with the new row number, which is going to be a different value with a differently-zoomed text size. So I want to react to text size changes with an “on” event that will recalculate this)
So we have these “mouse-based” ons:
ON DBLCLICK [command]
ON LBUTTON [command]
ON MBUTTON [command]
ON RBUTTON [command]
These are great. I don’t even really know how to use them, but I’m excited they exist.
I’m in a situation where I want to respond to the text size being increased. Which is, specifically for me, Ctrl-MouseWheelUp / Ctrl-MouseWheelDown.
It’s another mouse-based event, but there’s no corresponding “on” handler for it.
(It turns out if you lock certain rows to be non-scrollable, your cursor can either be in the normal part, or the locked part -- typically a 1–3 line statusbar. You can end up getting trapped inside the status bar if and only if the text size is changed without re-segregating the status bar with the new row number, which is going to be a different value with a differently-zoomed text size. So I want to react to text size changes with an “on” event that will recalculate this)