Maximized area state with a singular area in a window has confusing side-effects #116210
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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 & 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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
Asset System
Module
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#116210
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.42
Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash:
9be62e85b727
Worked: N/A
Short description of error
When you have only one UI area in a window, you can still maximize that one. It makes no difference visually, but precludes clicking and dragging the upper left area corner to split it up.
One can run into this situation by accident and find themselves unable to split an area with no visual indication why.
Exact steps for others to reproduce the error
Start Blender and make a new scene (excuse the UI scaling, I'm working on a bigger monitor)
Shift+click and drag the upper left area corner upwards to make a new area window
Hit Ctrl+Space to maximize the area in the new window.
It is now not possible to click and drag the upper left corner inside of that area anymore to split it or copy it into yet another new window, and the reason for this is not visually apparent.
I'm not sure what other behavior of the UI changes when an area is maximized. With what I'm seeing here, it would make sense that if there is only one area in the window, maximizing it should be disabled (but restoring to non-maximized allowed, in case somebody saved their .blend file like that).
🙂
Hi, thanks for the report. This is not a bug. Poll function of split/join/swap operation do not allow to execute it in case of maximized area, see: https://projects.blender.org/blender/blender/src/branch/main/source/blender/editors/screen/screen_ops.cc#L697
@PratikPB2123 I understand this, but it's not what I meant...
You are saying that it is correct that a maximized area can't be split. I agree with that!
What I'm saying is that it would be better if an area couldn't be maximized if it was the only area in the window, because there's no indication for this and can feel wrong to somebody who maximized it by accident.