Anyone else used a Logitech touch mouse? Or the Apple thing?
I’ve been threatening to throw mine in the garbage for 10 years. In some programs it is a total PITA.
And yet… it could be so perfect.
I’d go a global override that requires the Control key to be pressed for the touch on the mouse to be activated. It’s the touch and bumping that is the issue.
I’ve been working in Resolve, I cannot find a place to put the menu bar where I don’t bump the side of the screen and cause it to fly out. That disappearing menu bar has been a PITA on every OS where it is used.
WHY IS IT SO?
I don’t get it. There are multiple options for the menu bar and none of them is “rack off and don’t come back until I hit the meta key”.
These 2 issues combined create a sucky user experience with this configuration (touch mouse).
I think Logitech only sold this touch mouse for a year. Still they are popular for Apple. They are pretty neat at what they do. It just all fails in Inkscape when you hand brushes the mouse and the page scrolls off.
I’m stuck on Plasma 5. If there were changes that impact the above in P6, tell me.
Is there any hidden keys or methods to achieve the above? Like just setting the touch for the menu to zero or something?
Am I the only one using a touch mouse? Am I the only one that hits that screen edge and cause menu hell?
I kinda don’t think I’m that unique. 
Hi - well, as long as you’re using “menu bar” to refer to the panel with the application menu, task buttons and system tray, then yours isn’t a totally unheard-of concern - hopefully you can take some solace in that! Show/hide main panel with a hotkey
And there is a pretty long-standing submitted feature request on that topic: 158556 – "Manual show" option for hidden panel controlled only by pushing a button on a widget somewhere else
With the extent of discussion that’s happened over the years, it looks like something that just needs a person with the time, interest and ability to dive in and figure out how to implement it
If that might be you or someone you know, the KDE Community Wiki has a great resource for getting started working on and contributing code: Get Involved/development - KDE Community Wiki
I’m personally an “always visible” panel user, so I’d have to defer to others for any hacky ideas to work around that situation - although it might be worthwhile playing around with different pointer speed or acceleration settings, if it’s been a while since you’ve done that?
“I’m personally an “always visible” panel user”
That’s likely the only option that works. To me that is 2/3 of a timeline in Resolve lost to scrolling.
It’s just so odd that on Linux and Windows this has never been addressed. I’m guessing the Mac is the same. And with so much finely tuned customization.
I’m sorry I can’t do this for us. How about I give $100 to someone who will?
I couldn’t build it either, just something that I’ll throw out there if there are folks who happen to be in the right spot for it
I suppose one workaround idea might be an always-visible panel, but extremely thin? At a height of 20, the panel seems like it barely takes up any room at all, and the clickability would still be OK since everything is up against the edge (Fitts’ Law benefit).
Even on a UHD monitor, that space is precious. When using Resolve the pros turn on and off the Resolve bar to make space.
That’s the problem, but my question is why is this done on both Windows and Linux when it is do obvious that this has been needed since the first use of the menubar/panel?
Making the bar smaller might be the only current workable solution.
It feels like, “we cannot have the menubar attached to the meta key and not visible because the people won’t find the menu”.
Like there was some strange conspiracy in UI land that user because too stupid to find the meta key. “We cannot possibly do that. We did that once and it caused a flood of help requests to find the bar.”
Microsoft make a lot of awful UI that way.