Vertical Scrollbar sensitivity and difference to Horizontal Scrollbar #118550

Closed
opened 2024-02-21 10:06:35 +01:00 by Gerstmann Bradley · 18 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 531.61

Blender Version
Broken: version: 4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-02-20 18:18, hash: a3ffb51da6c5

Caused by 809499a3d0

Short description of error

  1. Vertical Scrollbar has less sensitivity in 4.1, it makes the scrollbar very heavy to move. Horizontal scrollbar has similar issue but in a much smaller extent. Interestingly, in the spreadsheet, only downwards movement is heavy, but upwards movement seems ideal.
  2. For unknown reason, vertical scrollbar sometimes doesn't move.
  3. In the spreadsheet, vertical scrollbar also shows a weird acceleration in the initial section.

last time an issue regarding to vertical scrollbar was reported in #117572. I think the fix still isn't ideal overall.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 531.61 **Blender Version** Broken: version: 4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-02-20 18:18, hash: `a3ffb51da6c5` Caused by 809499a3d0a2ef17c612f5e970cbed9ad4fb750d **Short description of error** 1. Vertical Scrollbar has less sensitivity in 4.1, it makes the scrollbar very heavy to move. Horizontal scrollbar has similar issue but in a much smaller extent. Interestingly, in the spreadsheet, only downwards movement is heavy, but upwards movement seems ideal. 2. For unknown reason, vertical scrollbar sometimes doesn't move. 3. In the spreadsheet, vertical scrollbar also shows a weird acceleration in the initial section. last time an issue regarding to vertical scrollbar was reported in https://projects.blender.org/blender/blender/issues/117572. I think the fix still isn't ideal overall.
Gerstmann Bradley added the
Status
Needs Triage
Priority
Normal
Type
Report
labels 2024-02-21 10:06:36 +01:00
Member

Before digging deeper (I can confirm a regression in the panels of the Filebrowser, that seems to be a regression from 83dbbf9aec rather than ed556113ce, that was really caused by 809499a3d0), I want to be as clear as possible:

For unknown reason, vertical scrollbar sometimes doesn't move

I cant spot this in the videos you shared (not can I reproduce this), can you try to explain/show this in detail?

In the spreadsheet, vertical scrollbar also shows a weird acceleration in the initial section.

This was the case in 4.0 / 3.6 LTS or previous versions as well right? (so it is not a regression from ed556113ce nor 83dbbf9aec

Before digging deeper (I can confirm a regression in the panels of the Filebrowser, ~~that seems to be a regression from 83dbbf9aecc3 rather than ed556113ce~~, that was really caused by 809499a3d0), I want to be as clear as possible: >For unknown reason, vertical scrollbar sometimes doesn't move I cant spot this in the videos you shared (not can I reproduce this), can you try to explain/show this in detail? >In the spreadsheet, vertical scrollbar also shows a weird acceleration in the initial section. This was the case in 4.0 / 3.6 LTS or previous versions as well right? (so it is not a regression from ed556113ce nor 83dbbf9aecc3
Philipp Oeser added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-02-21 10:59:40 +01:00

I cant spot this in the videos you shared (not can I reproduce this), can you try to explain/show this in detail?

in "Vertical Scrollbar" at 0:08. I tried 3 times to move the scrollbar but it doesn't work. The scrollbar was highlighted so it must be selected. I am not yet sure the exact behavior triggering it, it occurs randomly in filebrowser.
When trying to reproduce this issue, I usually scroll the top scrollbar downwards and back to the original position, and then scroll the lower and back to the original position, going back to the top scrollbar, and again scroll the lower one. Repeating this until I trigger the bug somehow.

Note, this issue can occur in both scrollbar in the filebrowser (didn't check spreadsheet).

Also to note, there's actually also a weird jumping behavior sometimes when I click onto the scrollbar in filebrowser. (didn't check spreadsheet.)

This was the case in 4.0 / 3.6 LTS or previous versions as well right?

Yes, I can reproduce it in 4.0.3 Release Candidate, branch: blender-v4.0-release, commit date: 2024-01-09 17:29, hash: 88559c00cd36

> I cant spot this in the videos you shared (not can I reproduce this), can you try to explain/show this in detail? in "Vertical Scrollbar" at 0:08. I tried 3 times to move the scrollbar but it doesn't work. The scrollbar was highlighted so it must be selected. I am not yet sure the exact behavior triggering it, it occurs randomly in filebrowser. When trying to reproduce this issue, I usually scroll the top scrollbar downwards and back to the original position, and then scroll the lower and back to the original position, going back to the top scrollbar, and again scroll the lower one. Repeating this until I trigger the bug somehow. Note, this issue can occur in both scrollbar in the filebrowser (didn't check spreadsheet). Also to note, there's actually also a weird jumping behavior sometimes when I click onto the scrollbar in filebrowser. (didn't check spreadsheet.) >This was the case in 4.0 / 3.6 LTS or previous versions as well right? Yes, I can reproduce it in 4.0.3 Release Candidate, branch: blender-v4.0-release, commit date: 2024-01-09 17:29, hash: `88559c00cd36`
Philipp Oeser added
Status
Needs Triage
and removed
Status
Needs Information from User
labels 2024-02-21 11:08:02 +01:00
Member

Will confirm and put on my desk to check further

Will confirm and put on my desk to check further
Philipp Oeser added
Status
Confirmed
Module
User Interface
and removed
Status
Needs Triage
labels 2024-02-22 11:18:44 +01:00
Philipp Oeser self-assigned this 2024-02-24 08:15:54 +01:00
Member

Oops, somehow missed to put this on High priority [it should have from the beginning...]

@JulianEisel : do you have time to look at this today? (have another High prio issue to fix)

Oops, somehow missed to put this on High priority [it should have from the beginning...] @JulianEisel : do you have time to look at this today? (have another High prio issue to fix)
Philipp Oeser removed their assignment 2024-03-21 08:28:26 +01:00
Philipp Oeser added
Priority
High
and removed
Priority
Normal
labels 2024-03-21 08:28:40 +01:00
Philipp Oeser added this to the 4.1 milestone 2024-03-21 08:28:44 +01:00
Member

Actually... I think this has been fixed (between 7f43699ebf50..b0daa792d3b5), will double-check

Actually... I think this has been fixed (between 7f43699ebf50..b0daa792d3b5), will double-check
Member

So, apparently the issue with the scrollbars in the Filebrowser somehow got fixed by 8c63889241

So (at least on my side) the situation of the original report description seems as follows:

  • Vertical Scrollbar has less sensitivity in 4.1
    -- was somehow caused by 83dbbf9aec 809499a3d0, was somehow fixed by 8c63889241 [in main, not in 4.1 though!]
    -- this seems fine for 4.2, not for 4.1 though and for 3.6 LTS we have this situation:
    --- ed556113ce is in there, but 83dbbf9aec isnt (because it had the followup issue from this very report)
    --- now 8c63889241 I am not sure if we can backport?
  • for unknown reason, vertical scrollbar sometimes doesn't move
    -- still could not reproduce
  • In the spreadsheet, vertical scrollbar also shows a weird acceleration in the initial section
    -- not a regression, should probably be split in a separate report

@Bradley_G : can you confirm that 1. and 2. are now working properly in a fresh 4.1 build from https://builder.blender.org/download/daily/?

@JulianEisel @HooglyBoogly would be good if you could double-check 1. and 2. are working fine for you as well in 4.1 onwards
@JulianEisel @HooglyBoogly opinions about the situation in 3.6 LTS?

So, apparently the issue with the scrollbars in the Filebrowser somehow got fixed by 8c63889241e0031ce9c80df053c344bec8d15042 So (at least on my side) the situation of the original report description seems as follows: - **Vertical Scrollbar has less sensitivity in 4.1** -- was somehow caused by ~~83dbbf9aec~~ 809499a3d0, was somehow fixed by 8c63889241e0 [in main, not in 4.1 though!] -- this seems fine for 4.2, not for 4.1 though and for 3.6 LTS we have this situation: --- ed556113ce is in there, but 83dbbf9aec isnt (because it had the followup issue from this very report) --- now 8c63889241e0 I am not sure if we can backport? - **for unknown reason, vertical scrollbar sometimes doesn't move** -- still could not reproduce - **In the spreadsheet, vertical scrollbar also shows a weird acceleration in the initial section** -- not a regression, should probably be split in a separate report @Bradley_G : can you confirm that 1. and 2. are now working properly in a fresh 4.1 build from https://builder.blender.org/download/daily/? @JulianEisel @HooglyBoogly would be good if you could double-check 1. and 2. are working fine for you as well in 4.1 onwards @JulianEisel @HooglyBoogly opinions about the situation in 3.6 LTS?

@lichtwerk I can still reproduce 1 & 2 in 4.1.
The recorded video is done from blender version committed on Mar.16, and I can see similar behavior on
4.1.0 Release Candidate, branch: blender-v4.1-release, commit date: 2024-03-20 22:16, hash: ddcfc46ee657
(In the video I was also trying to investigate what can trigger scroll bar not moving sometimes, but I still can't be sure.)

On the contrary, 4.2 is absolutely fine for 1 and probably 2.
4.2.0 Alpha, branch: main, commit date: 2024-03-21 00:15, hash: 2df06a05ae68

also for 3. should I report it separately now or?

@lichtwerk I can still reproduce 1 & 2 in 4.1. The recorded video is done from blender version committed on Mar.16, and I can see similar behavior on 4.1.0 Release Candidate, branch: blender-v4.1-release, commit date: 2024-03-20 22:16, hash: `ddcfc46ee657` (In the video I was also trying to investigate what can trigger scroll bar not moving sometimes, but I still can't be sure.) On the contrary, 4.2 is absolutely fine for 1 and probably 2. 4.2.0 Alpha, branch: main, commit date: 2024-03-21 00:15, hash: `2df06a05ae68` also for 3. should I report it separately now or?
Member

Thx getting back @Bradley_G !

I can actually repro the scrollbar sensitivity issue in 4.1 from the bot as well.
Not sure what went wrong in bisect, will give it another round...

Thx getting back @Bradley_G ! I can actually repro the scrollbar sensitivity issue in 4.1 from the bot as well. Not sure what went wrong in bisect, will give it another round...
Member

also for 3. should I report it separately now or?

yes, please

> also for 3. should I report it separately now or? yes, please
Member

Thx getting back @Bradley_G !

I can actually repro the scrollbar sensitivity issue in 4.1 from the bot as well.
Not sure what went wrong in bisect, will give it another round...

Hm, did another test, and reconfirming that 8c63889241 did indeed fix it for me in main (not sure why this is not effective in 4.1)

> Thx getting back @Bradley_G ! > > I can actually repro the scrollbar sensitivity issue in 4.1 from the bot as well. > Not sure what went wrong in bisect, will give it another round... Hm, did another test, and reconfirming that 8c63889241 did indeed fix it for me in main (not sure why this is not effective in 4.1)
Member

not sure why this is not effective in 4.1

It was committed to 4.1 when someone merged main into 4.1 :/ Then reverted later.

>not sure why this is not effective in 4.1 It was committed to 4.1 when someone merged main into 4.1 :/ Then reverted later.
Member

not sure why this is not effective in 4.1

It was committed to 4.1 when someone merged main into 4.1 :/ Then reverted later.

Haha, that makes sense then :)

> >not sure why this is not effective in 4.1 > > It was committed to 4.1 when someone merged main into 4.1 :/ Then reverted later. Haha, that makes sense then :)
Member

Having been still puzzled that 83dbbf9aec caused this, I think it actually didnt, will now do a proper bisect, sorry for all this noise

Having been still puzzled that 83dbbf9aec caused this, I think it actually didnt, will now do a proper bisect, sorry for all this noise
Member

OK, so it was really caused by 809499a3d0

@HooglyBoogly : could we just cherry-pick 8c63889241 to 4.1-release and be done?

OK, so it was really caused by 809499a3d0a2ef17c612f5e970cbed9ad4fb750d @HooglyBoogly : could we just cherry-pick 8c63889241 to 4.1-release and be done?

At this point safer to have this in 4.1.1 only.

At this point safer to have this in 4.1.1 only.
Thomas Dinges removed this from the 4.1 milestone 2024-03-25 11:22:56 +01:00
Member

An update: I tried cherry-picking that commit and it didn't work. I expect it's the series of followup commits that fixed the issue in main. I also tried reverting the "caused by" commit in main and that was tricky because it's part of a series of commits. Then I tried reverting a bunch of the refactors in 4.1, and no luck with that either.

An update: I tried cherry-picking that commit and it didn't work. I expect it's the series of followup commits that fixed the issue in main. I also tried reverting the "caused by" commit in main and that was tricky because it's part of a series of commits. Then I tried reverting a bunch of the refactors in 4.1, and no luck with that either.

@HooglyBoogly We can also leave this for 4.2 then.

@HooglyBoogly We can also leave this for 4.2 then.
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2024-04-05 18:30:20 +02:00
Member

Testing this in 4.1, I didn't get the impression that this issue was so blocking. What I observed was more like some weirdness when first dragging the scroll bar. Because of that, because it's resolved in 4.2,, and the fact that the fix is tricky in 4.1, I think it's reasonable to close this.

Edit: I see @Bradley_G has already closed it, thanks.

Testing this in 4.1, I didn't get the impression that this issue was so blocking. What I observed was more like some weirdness when first dragging the scroll bar. Because of that, because it's resolved in 4.2,, and the fact that the fix is tricky in 4.1, I think it's reasonable to close this. Edit: I see @Bradley_G has already closed it, thanks.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#118550
No description provided.