Page MenuHome

long scrolled areas do not revert when switching objects
Closed, ResolvedPublic


System Information
Mac OSX 10.9.5, NVIDIA card

Blender Version
Broken: 2.75 RC2 Hash: c85a58a
Worked: ??

Short description of error
I had an object with a long list of modifiers, and scrolled to the bottom of the list. I then selected an object with a much shorter list of modifiers. The scroll bar stayed at the bottom, as if the second object's modifier list was as long as the first, until I scrolled up all the way, at which point i could no longer scroll down again into the empty space.

This gave me the false impression that there were no modifiers on the second object.

Exact steps for others to reproduce the error
1 - open bug_report.blend
2 - select Cube_long
3 - scroll to the bottom of Cube_long's modifier list
4 - select Cube_short
5 - look at modifier list.
5 - scroll up. You'll notice the length of the scroll bar changes as you scroll. You can no longer scroll down.

Event Timeline

Mark (markbosz) set Type to Bug.
Mark (markbosz) added a subscriber: Mark (markbosz).
Mark (markbosz) created this task.
Mark (markbosz) raised the priority of this task from to Needs Triage by Developer.
Bastien Montagne (mont29) closed this task as Invalid.
Bastien Montagne (mont29) claimed this task.

Thanks for the report, but this is not a bug, rather a feature (allows you to switch between objects and find again what you were working on when switching back)… Code is working as expected anyway.

I agree with @Mark (markbosz) that this is bad UX.

allows you to switch between objects and find again what you were working on when switching back

That would be useful only if it remembered scroll position per object.

@Mark Fernandes (mark), @Paweł Łyczkowski (plyczkowski), unfortunately, this "bad UX" is happening in other cases as well. Like when opening a panel or dragging items outside of view bounds. They're not hard to fix, but this is rather low in priority IMHO. I'll definitely check it at some point though.

I can confirm this is happening on Linux too.
I'd say this is a bug (albiet a low priority one): the scrollbar is suppose to calculate the window size, but in this case skips the window size is wrong, presumably not getting notification that the contents changed.
If it is a hard bug to fix, it might be best postponed, but if it is easy, maybe @Campbell Barton (campbellbarton) would like to add it to the 'easy tasks list for new developers' (sic) ?