Changes to window sizes or rearranged quick access panel components are not saved consistently (reopened) #85052

Closed
opened 2021-01-25 18:45:53 +01:00 by Daniel L. Travieso · 11 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30

Blender Version
Broken: version: 2.92.0 Beta, branch: master, commit date: 2021-01-22 18:24, hash: a1f44e43a2
Worked: (newest version of Blender that worked as expected)

Short description of error
Changes in window sizes or rearranged components are not saved.

Exact steps for others to reproduce the error

  • Go to EDIT -> PREFERENCES
  • Increase the size of the Preferences window by dragging it by the frame edge
  • Close the Preferences window
  • Open the Preferences window again by going to EDIT -> PREFERENCES
    The Preferences window size is back to its original size despite you increasing the size earlier

Same goes for changes in the panels, example:

  • Go to FILE -> IMPORT -> COLLADA
  • Resize the import file window that opened
  • Rearrange the components in the quick access panel on the left of that window, i.e. swap the position of VOLUMES and SYSTEM by dragging them by their handle (::::)
  • Close the window
  • Reopen the window with FILE -> IMPORT -> COLLADA
    You will notice it saved the resizing of this window, but it did not save the rearranged quick access panel components

It works in some cases but not consistently across the program. I took the time to report this in detail, don't give me a one-liner claiming it's not a bug just to get rid of it. It may not seem important to you but it is to me. What is the point of having arrange-able panel components if the changes are not saved? Why are some window sizes saved and others not? Clearly a bug. Are you expecting us to reconfigure the program to our needs every time we open the program?

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30 **Blender Version** Broken: version: 2.92.0 Beta, branch: master, commit date: 2021-01-22 18:24, hash: `a1f44e43a2` Worked: (newest version of Blender that worked as expected) **Short description of error** Changes in window sizes or rearranged components are not saved. **Exact steps for others to reproduce the error** - Go to EDIT -> PREFERENCES - Increase the size of the Preferences window by dragging it by the frame edge - Close the Preferences window - Open the Preferences window again by going to EDIT -> PREFERENCES The Preferences window size is back to its original size despite you increasing the size earlier Same goes for changes in the panels, example: - Go to FILE -> IMPORT -> COLLADA - Resize the import file window that opened - Rearrange the components in the quick access panel on the left of that window, i.e. swap the position of VOLUMES and SYSTEM by dragging them by their handle (::::) - Close the window - Reopen the window with FILE -> IMPORT -> COLLADA You will notice it saved the resizing of this window, but it did not save the rearranged quick access panel components It works in some cases but not consistently across the program. I took the time to report this in detail, don't give me a one-liner claiming it's not a bug just to get rid of it. It may not seem important to you but it is to me. What is the point of having arrange-able panel components if the changes are not saved? Why are some window sizes saved and others not? Clearly a bug. Are you expecting us to reconfigure the program to our needs every time we open the program?

Added subscriber: @Yps

Added subscriber: @Yps
Member

Closed as duplicate of #62725

Closed as duplicate of #62725
Member

Added subscriber: @filedescriptor

Added subscriber: @filedescriptor
Member

Again. This is not a bug but a limitation. It is working as intended.

Again. This is not a bug but a limitation. It is working as intended.

Weird, the import window size changes are saved, but others not. That is in a Python environment a very odd "limitation". I don't think you know what you're doing.

Weird, the import window size changes are saved, but others not. That is in a Python environment a very odd "limitation". I don't think you know what you're doing.

Added subscriber: @rjg

Added subscriber: @rjg

@Yps There are multiple windows that have a hardcoded default sizes that they open with, including the user preferences, drivers editor and info log. Currently the size of these windows aren't stored. Making the window size persistent would be a design decision for the UI module to make, but as @filedescriptor stated, this is currently not considered a bug. Please keep in mind that we use a very narrow definition of what a bug is on the bug tracker. This is a feature that doesn't exist at the moment, but not a broken functionality.

@Yps There are multiple windows that have a hardcoded default sizes that they open with, including the user preferences, drivers editor and info log. Currently the size of these windows aren't stored. Making the window size persistent would be a design decision for the UI module to make, but as @filedescriptor stated, this is currently not considered a bug. Please keep in mind that we use a very narrow definition of what a bug is on the bug tracker. This is a feature that doesn't exist at the moment, but not a broken functionality.

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel

@JulianEisel Tagging you here so that you are aware of the complaint about the inconsistency of stored window sizes w.r.t. UX.

@JulianEisel Tagging you here so that you are aware of the complaint about the inconsistency of stored window sizes w.r.t. UX.
Member

Like Falk and Robert said, this is working as intended. On one side it is a limitation of the 2.5 window-manager design that doesn't include such aspects (being based on the non-overlapping paradigm ). But it is also a design topic: Why would somebody want this? Because the default window size doesn't work well in all cases? Maybe the default should be changed? Or maybe the window size should change based on the content?

I don't understand what this has to do with Python, there is no Python involved in this.

For the file browser I added support for remembering the size (and some other settings), because it was important for the new file browser design to work well. There are many other issues with multi-window workflows and temporary windows that I see as more important. Unfortunately this isn't simple to do well on all platforms.

Like Falk and Robert said, this is working as intended. On one side it is a limitation of the 2.5 window-manager design that doesn't include such aspects (being based on the [non-overlapping paradigm ](https://archive.blender.org/wiki/index.php/Dev:2.5/Source/UI/UIParadigms/)). But it is also a design topic: Why would somebody want this? Because the default window size doesn't work well in all cases? Maybe the default should be changed? Or maybe the window size should change based on the content? I don't understand what this has to do with Python, there is no Python involved in this. For the file browser I added support for remembering the size (and some other settings), because it was important for the new file browser design to work well. There are many other issues with multi-window workflows and temporary windows that I see as more important. Unfortunately this isn't simple to do well on all platforms.

Why would somebody want this?
Well, to put it in your own words: because it is important for the new [..] design to work well.

I understand you got a lot on your hands, but you tell us to report things that bother us. So here I am, telling you what bothers me the most, having to resize the windows every time I need to access them just so I can get a little bit more of an overview of what is cluttered in there. I'm no Blender genius. I have been studying this software for quite some time but I am still struggling because it is all still very cluttered and not very intuitive. And it's frustrating to have to do this every. single. time. Ok, fine, it's not a bug. But it sure is bugging me.

Why would somebody want this? Well, to put it in your own words: because it is important for the new [..] design to work well. I understand you got a lot on your hands, but you tell us to report things that bother us. So here I am, telling you what bothers me the most, having to resize the windows every time I need to access them just so I can get a little bit more of an overview of what is cluttered in there. I'm no Blender genius. I have been studying this software for quite some time but I am still struggling because it is all still very cluttered and not very intuitive. And it's frustrating to have to do this every. single. time. Ok, fine, it's not a bug. But it sure is bugging me.
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#85052
No description provided.