Is it possible to "lock" the vertical scroll when the mouse is hovering over an action with its own scroll such as shell, applescript, etc?
One of the things that always bothered me is that when I scroll to see the content on one of those windows, 90% of the time it scrolls it a little bit, then it reverts to scrolling the whole macro. I'm not a fan of manually clicking the scroll bar to use it. I like the scroll wheel (that's why it was invented... right?).
It seems, not sure if by accident, that sometimes holding shift, cmd, or alt/option seems to kinda lock it, but not 100%. It decreases the chances of it scrolling the macro to maybe 20%, but still not perfect.
Is there a way to achieve this by changing some setting or using a different modifier key?
If not, would this be possible to implement, for those of you who are more familiar with how KM works behind the scenes in terms of UI and all that?
Would like to get some feedback before approaching Peter about this issue.
Yeah it is annoying. I've found that by clicking inside the scrolling area usually lets me scroll normally without having the whole macro scroll. Have you tried that?
My guess is that Peter will say the KM Editor's behaviour is limited by the tools and APIs he uses to create the Editor. Since this is normal behaviour for other apps like Safari, the API developers probably consider it an acceptable problem.
KM honours the System Setting "Appearance"->"Show scroll bars".
A total abomination of a default setting from Apple's "make it look like iOS" phase, and I urge every right-thinking person to hit the "Always" radio button ASAP...
I don't know the intricacies of building an app, but if using a modifier could lock the macro's scrolling completely (whatever makes all actions go up and down), that would be a step forward, I guess. So locking it with a custom key combination set by the user would make the macro non-scrollable, while maybe allowing the action's text scroll?
Again, I have no idea what's happening in the background, so this is just a suggestion. Maybe others here can share their feedback on why this could/couldn't work?
As an audio and video editor, there are simply far too many moving parts to even try to make do with the hardware of a normal mouse. The way my screen jumping around was slowing my work down constantly drove me to expand those inputs.. ending up in places like this forum
"Trackballs" are the standard solution, with a scroll wheel.
If you lift slightly, the wheel finger can turn it independently , reducing to 1-2% of that 20% mentioned above of missed, intended scrolls.
Sometimes people feel they are bulky for some operations. I like to use a flat trackpad beside the trackball, too. I go back and forth.
