Subpanels flicker when expanding panel that has moved #79014

Open
opened 2020-07-17 07:06:41 +02:00 by Braden Currah · 8 comments

System Information
Operating system: Windows-10-10.0.20161-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87

Blender Version
Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-12 09:05, hash: f319eec881
Worked: Persistent issue throughout 2.8x.

Short description of error
Certain combinations of minimizing and maximizing the physics properties panels (described below) will cause the element to flash near the bottom of the screen for a frame.

Exact steps for others to reproduce the error

  1. With any object selected, enable two (or more) physics properties for the object.
  2. Minimize the final panel, and then the first.
  3. Maximize the final panel.

Observations
The differences previously mentioned are simply due to a lack of subpanels or panel length.
A second jump appears to sometimes happen when maximizing the final panel after changing the panel type, though I cannot reproduce this reliably.

If the formatting of this video is as terrible as it seems, please let me know how to fix it.
ezgif.com-crop.mp4

**System Information** Operating system: Windows-10-10.0.20161-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87 **Blender Version** Broken: version: 2.90.0 Alpha, branch: master, commit date: 2020-07-12 09:05, hash: `f319eec881` Worked: Persistent issue throughout 2.8x. **Short description of error** Certain combinations of minimizing and maximizing the physics properties panels (described below) will cause the element to flash near the bottom of the screen for a frame. **Exact steps for others to reproduce the error** 1. With any object selected, enable two (or more) physics properties for the object. 2. Minimize the *final* panel, and then the first. 3. Maximize the final panel. **Observations** The differences previously mentioned are simply due to a lack of subpanels or panel length. A second jump appears to sometimes happen when maximizing the final panel after changing the panel type, though I cannot reproduce this reliably. If the formatting of this video is as terrible as it seems, please let me know how to fix it. [ezgif.com-crop.mp4](https://archive.blender.org/developer/F8700803/ezgif.com-crop.mp4)
Author

Added subscriber: @TakingFire

Added subscriber: @TakingFire
Braden Currah changed title from Interface flicker when minimizing physics panels to Interface flicker when maximizing physics panels 2020-07-17 07:22:44 +02:00

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'

I can confirm.
I also saw the same behavior on the modifier panels.
I can't reproduce the problem in 2.80

I can confirm. I also saw the same behavior on the modifier panels. I can't reproduce the problem in 2.80
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

Interesting. Here is the offending frame of the animation:
image.png
The key information is that the locations of subpanels don't update while their parent panel is closed. So because the collision
panel is closed first, the subpanels are left at the bottom of the region. Then the first panel is closed, moving the collision panel
up, so when it opens again its subpanels are still at the bottom for a single frame.

I wonder why the subpanel locations don't update on the same redraw as the panel is drawn open.

Interesting. Here is the offending frame of the animation: ![image.png](https://archive.blender.org/developer/F8701809/image.png) The key information is that the locations of subpanels don't update while their parent panel is closed. So because the collision panel is closed first, the subpanels are left at the bottom of the region. Then the first panel is closed, moving the collision panel up, so when it opens again its subpanels are still at the bottom for a single frame. I wonder why the subpanel locations don't update on the same redraw as the panel is drawn open.
Member

Added subscribers: @JulianEisel, @ideasman42

Added subscribers: @JulianEisel, @ideasman42
Member

In #79014#980977, @HooglyBoogly wrote:
I wonder why the subpanel locations don't update on the same redraw as the panel is drawn open.

Okay, this is because the panel header handler operates on the panel right before the next redraw, but the panel alignment code happens
in the layout step, which happens before drawing. The process looks like this:

Layout Draw Handlers (close panel) Draw (Bad subpanel offset) Layout (corrects subpanel offsets) Draw etc..
I see two possible solutions:
  1. Refactor the panel alignment code so that it runs at the start of the drawing phase if necessary.
  2. Align subpanels whether they are visible or not.

The 2nd option is definitely quicker, but I'm not sure I like it as much. Figuring out whether to align or not is the worst part of the panel code
right now IMO, maybe it would be good to refactor that anyway. I'd be interest to hear @JulianEisel's / @ideasman42's opinion though.

> In #79014#980977, @HooglyBoogly wrote: > I wonder why the subpanel locations don't update on the same redraw as the panel is drawn open. Okay, this is because the panel header handler operates on the panel right before the next redraw, but the panel alignment code happens in the `layout` step, which happens before drawing. The process looks like this: |Layout|Draw|Handlers **(close panel)**|Draw **(Bad subpanel offset)**|Layout **(corrects subpanel offsets)**|Draw|etc..| | -- | -- | -- | -- | -- | -- | -- | I see two possible solutions: 1. Refactor the panel alignment code so that it runs at the start of the drawing phase if necessary. 2. Align subpanels whether they are visible or not. The 2nd option is definitely quicker, but I'm not sure I like it as much. Figuring out whether to align or not is the worst part of the panel code right now IMO, maybe it would be good to refactor that anyway. I'd be interest to hear @JulianEisel's / @ideasman42's opinion though.
Hans Goudey changed title from Interface flicker when maximizing physics panels to Subpanels flicker when expanding panel that has moved 2020-07-17 18:24:36 +02:00
Philipp Oeser removed the
Interest
User Interface
label 2023-02-10 09:24:14 +01:00
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
3 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#79014
No description provided.