Toggle Quad View doesn't really toggle, it forgets user state. #39039

Closed
opened 2014-03-08 08:56:08 +01:00 by mattali · 14 comments
mattali commented 2014-03-08 08:56:08 +01:00 (Migrated from localhost:3001)

System Information
All OS and GC

Blender Version
Broken: 2.70rc

Short description of error
THis report follows this discussion on stackoverflow : . While toggling Quad view, unlike Numpad0 for camera view, it switch like that : User point of view, quadview with camera view, random orthoview, quadview with camera view, random orthoview, etc... destroying user point of view. We tried many workarounds, even writing some python code, without success.

Exact steps for others to reproduce the error
Default scene, hit N, click on toggle quad view twice.

**System Information** All OS and GC **Blender Version** Broken: 2.70rc **Short description of error** THis report follows [this ](http://blender.stackexchange.com/questions/7590/is-there-a-way-to-make-an-operator-know-if-the-context-viewport-is-in-ortho-or-p) discussion on stackoverflow : . While toggling Quad view, unlike Numpad0 for camera view, it switch like that : User point of view, quadview with camera view, random orthoview, quadview with camera view, random orthoview, etc... destroying user point of view. We tried many workarounds, even writing some python code, without success. **Exact steps for others to reproduce the error** Default scene, hit N, click on toggle quad view twice.
mattali commented 2014-03-08 08:56:08 +01:00 (Migrated from localhost:3001)
Author

Changed status to: 'Open'

Changed status to: 'Open'
mattali commented 2014-03-08 08:56:08 +01:00 (Migrated from localhost:3001)
Author

Added subscriber: @mattali

Added subscriber: @mattali
mattali commented 2014-03-08 09:00:28 +01:00 (Migrated from localhost:3001)
Author

Discussion was split actually, more can be found here

Discussion was split actually, more can be found [here ](http://blender.stackexchange.com/questions/7584/can-toggle-quad-view-remember-the-viewpoint)

Added subscriber: @kevindietrich

Added subscriber: @kevindietrich

Can't reproduce this here on Linux with ef51b69. I don't get some random other view each time, it only swithes back and forth between Quad view and Front Ortho view.

Can't reproduce this here on Linux with ef51b69. I don't get some random other view each time, it only swithes back and forth between Quad view and Front Ortho view.

Added subscribers: @brecht, @ideasman42, @mont29

Added subscribers: @brecht, @ideasman42, @mont29

This is not a bug indeed, yet current behavior is a bit confusing (even in programming/API POV). Currently:

  • When you switch to quadview, all orientations are overridden to get the top/front/right/cam views.
  • When you switch from quadview, the context-active view is kept, but when using button, it is always the "front" view (bottom left) one, the three other ones are lost. So this work rather nice with ctrl-Q, not so nice with button…

Not sure what to do… In P22, I propose following instead:

  • When you switch to quadview, set top/front/right orientations, but reuse current view orientation as "Camera" one (top-right).
  • When you switch from quadview, always reuse "Camera" view orientation.

This at least keeps things logical, also from API POV, since region_3d (the mono-view region) is also the one giving access to "Camera" view in quad mode.

Brecht, Campbell, thoughts?

This is not a bug indeed, yet current behavior is a bit confusing (even in programming/API POV). Currently: * When you switch **to** quadview, all orientations are overridden to get the top/front/right/cam views. * When you switch **from** quadview, the context-active view is kept, but when using button, it is always the "front" view (bottom left) one, the three other ones are lost. So this work rather nice with ctrl-Q, not so nice with button… Not sure what to do… In [P22](https://archive.blender.org/developer/P22.txt), I propose following instead: * When you switch **to** quadview, set top/front/right orientations, but reuse current view orientation as "Camera" one (top-right). * When you switch **from** quadview, always reuse "Camera" view orientation. This at least keeps things logical, also from API POV, since region_3d (the mono-view region) is also the one giving access to "Camera" view in quad mode. Brecht, Campbell, thoughts?
mattali commented 2014-03-09 09:54:11 +01:00 (Migrated from localhost:3001)
Author

@mont29 Thanks for the proposed fix. Looks good, maybe for consistency it would be good to make it work like the Numpad0 camera view toggle as it's about the same except you get 3 orthoviews with it. But at least with that fix, we could implement the behavior in a python operator that would save camera and viewport POV to allow usual toggling.

@mont29 Thanks for the proposed fix. Looks good, maybe for consistency it would be good to make it work like the Numpad0 camera view toggle as it's about the same except you get 3 orthoviews with it. But at least with that fix, we could implement the behavior in a python operator that would save camera and viewport POV to allow usual toggling.

@mont29, regarding your proposal.

Some issues -

  • When you switch to quad view, and you are in an axis-view (Right View) for example, should it keep using this view? (this may be confusing to have 2x Right views when entering quad-view).

  • When you switch out of quad view, using the top-right view makes sense, but only (IMHO) when your accessing it from a button. when using the key binding using the current view may be seen as a feature / useful.

@mont29, regarding your proposal. Some issues - - When you switch to quad view, and you are in an axis-view (Right View) for example, should it keep using this view? (this may be confusing to have 2x Right views when entering quad-view). - When you switch out of quad view, using the top-right view makes sense, but only (IMHO) when your accessing it from a button. when using the key binding using the current view may be seen as a feature / useful.

@mont29, rather not rush a fix for this in for 2.70 release. ok to move this to a design task?

@mont29, rather not rush a fix for this in for 2.70 release. ok to move this to a design task?
Bastien Montagne self-assigned this 2014-03-10 08:37:48 +01:00

@ideasman42 Sure, this is not for 2.70 anyway (not a regression nor critical bug).

When you switch to quad view, and you are in an axis-view (Right View) for example, should it keep using this view? (this may be confusing to have 2x Right views when entering quad-view).

I’d say yes, better to stay consistent here imho… And keeping current view, except if it matches ones of the three other ortho ones, might be confusing as well for user. No strong opinion though, both cases have pros and cons.

When you switch out of quad view, using the top-right view makes sense, but only (IMHO) when your accessing it from a button. when using the key binding using the current view may be seen as a feature / useful.

100% agree! In the quick patch I provided, I just could not find an easy way to distinguish between button/shortcut call…

@ideasman42 Sure, this is not for 2.70 anyway (not a regression nor critical bug). > When you switch to quad view, and you are in an axis-view (Right View) for example, should it keep using this view? (this may be confusing to have 2x Right views when entering quad-view). I’d say yes, better to stay consistent here imho… And keeping current view, except if it matches ones of the three other ortho ones, might be confusing as well for user. No strong opinion though, both cases have pros and cons. > When you switch out of quad view, using the top-right view makes sense, but only (IMHO) when your accessing it from a button. when using the key binding using the current view may be seen as a feature / useful. 100% agree! In the quick patch I provided, I just could not find an easy way to distinguish between button/shortcut call…
mattali commented 2014-04-01 20:23:28 +02:00 (Migrated from localhost:3001)
Author

@mont29 THanks a lot for your patch. Could it be integrated in trunk ?

@mont29 THanks a lot for your patch. Could it be integrated in trunk ?

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

This has been fixed by Campbell now (forth view just always remains the same as in non-quad-view mode).

This has been fixed by Campbell now (forth view just always remains the same as in non-quad-view mode).
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#39039
No description provided.