https://bugs.kde.org/show_bug.cgi?id=426716
Duncan <1i5t5.dun...@cox.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |1i5t5.dun...@cox.net
--- Comment #4 from Duncan <1i5t5.dun...@cox.net> ---
In bug #476047 comment #10 Frank asked if this bug was related to that one. I
replied (comment 11) saying I'd reply here to avoid spamming that bug.
First, thanks. It had never occurred to me to even try scrolling on the
breadcrumbs (I knew about clicking on them) so I never knew of that
functionality. Unfortunately the bug still seems to be there and a hi-rez
"pixel-scrolling" touchpad is my only pointing device so I can't really observe
the /intended/ behavior (I see something happens but it doesn't appear
particularly usable ATM with this type of device).
To your question (answering as not a dev, but as a user that tracks live-git
and is accustomed to "dev-speak" and doing the occasional simple patch of my
own): Yes, it's related, but in the sense that it seems every scroll-usage
needs its own code to treat hi-res/pixel-scrolling differently than mouse-wheel
incremental-click-scrolling. Apparently, there's no way to fix it once in the
input handling code and have it apply everywhere, tho fixing it in for example
the kio breadcrumbs-handler would fix it for the breadcrumbs component (but not
other components) of all apps that use it.
So until hi-rez/pixel-scrolling gets fixed for kio's breadcrumbs, looks like
clicking the arrow-separators and selecting the appropriate subdir will remain
the working UI for us.
The good news is that with the ports to wayland and to qt6 now basically done
and the totally-breaks-functionality bugs generally fixed, as evidenced by that
other bug, the devs seem to be focusing more on these "papercut" type bugs in
the UI where there were other working ways to do the same thing making it less
pressing to fix the still-broken ways. So while this bug has been basically
stalled for 4-1/2 years, there's some reasonable hope now for a fix in the next
(say) 2-6 months, and with any luck, your pointer on that other bug back to
this related one will be the trigger to get it fixed too! =:^)
--
You are receiving this mail because:
You are watching all bug changes.
