-
Notifications
You must be signed in to change notification settings - Fork 757
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scroll view issue in Qt -- no vertical scroll bar #1521
Comments
@edwardenixon - Which OS (and version) are you running? |
Sorry. OS X latest — 10.10.3. …edN
|
Yes, its some kind of auto-hiding setting. If you don't have a scroll wheel on your mouse then you can't scroll. Probably it works fine with the clever mac trackpad. |
There's an OS preference for this - I think the actual bug is that some of the lang views don't follow the OS pref. Documents in the IDE, for example, DO follow the OS preference. |
I’d be willing to bet (something) that a large majority of people, SC people at least, don’t know about an OS option to hide the scroll bar. And don’t care. I can’t imagine why one would want to do that. But then there’ve been some pretty bizarre things happening to the OS X interface in the last version: sliding pages, disappearing menus in full page, all happening auto-magically when someone simply wants the traditional behaviour of those three little dots in the upper left corner. I would hope that I don’t have to follow all that featuritis down its own particular rabbit hole. …edN
|
Here's the OS X system preference: I think we should be as normal as possible: its a system preference. On OS X it is smart: if your mouse can scroll then it uses auto. If your wheel is broken you can set it to Always. That's great, that's what OS are supposed to do. do you really mean show always ? I think we should let the OS call the shots. |
Yeah, haven't pull-req'd that branch yet, I have one more change that
On Fri, Jun 5, 2015, 12:49 AM Chris Sattinger notifications@github.com
|
operating systems and frameworks are great ... until they become annoying. On Fri, Jun 5, 2015 at 10:39 AM scztt notifications@github.com wrote:
|
I’m not finding that changing that setting makes any difference with the Quarks.gui statement. At least after an SC alpha1 restart; does it take effect after a reboot? What I just noticed however, is that the scroll bar makes a brief appearance just as the window has opened. Then it disappears. …edN
|
So - I can make this behave reasonably on mac. However, I'm not aware of calls on Windows / Linux to check whether the overlay (disappearing) scrollbars are appropriate (or to check for the presence of a mouse wheel). So, to fix this bug on those platforms, we'd have to show the scrollbars ALL the time... I don't love that solution, as the overlay scrollbars save screen real estate and the always-on scrollbars in Qt are, frankly, terrible looking. It's tough, because transient scrollbars are probably most appropriate for anyone that has a trackpad / wheel mouse, but are a complete deal-breaker without wheel support. One things I've done in the past to solve this sort of problem: default to the show-always behavior, and switch to autohide as SOON as you receive the first mouse wheel event. That way, users who don't have a mouse wheel / don't use it will always see scrollbars, but users who are wheelers will get the probably-more-appropriate auto-hide behavior. |
At least on my machine (Ubuntu Studio 14.04, Qt 5.21) scrollbars are always visible within the Quarks gui - doesn't bother me. Rather have them always visible instead of not being able to scroll if the mousewheel breaks somehow... |
Ubuntu 15 has a system-wide setting that enables/disables the overlay scrollbars - we should be honoring that. I think it's new, though.... |
Here! Here! …edN
|
fixed. |
Quarks.gui; brings up a window with no scroll bar.
Apparently, scrolling works for users with scroll wheel mice. Act of scrolling via whell reveals a scroll bar which can then be grabbed. Felix thinks it's a Qt flag needing setting.
The text was updated successfully, but these errors were encountered: