Page MenuHome
Create Task
Maniphest T39039

Toggle Quad View doesn't really toggle, it forgets user state.
Closed, ResolvedPublic
Actions

Description

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.

Related Objects

Event Timeline

• matali (mattali) created this task.Mar 8 2014, 8:56 AM
• matali (mattali) raised the priority of this task from to 90.
• matali (mattali) updated the task description. (Show Details)
• matali (mattali) added a project: BF Blender.
• matali (mattali) edited a custom field.
• matali (mattali) added a subscriber: • matali (mattali).
• matali (mattali) added a comment.Mar 8 2014, 9:00 AM

Discussion was split actually, more can be found here

Kévin Dietrich (kevindietrich) added a subscriber: Kévin Dietrich (kevindietrich).Mar 8 2014, 11:34 AM

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.

Bastien Montagne (mont29) added subscribers: Brecht Van Lommel (brecht), Campbell Barton (campbellbarton), Bastien Montagne (mont29).Mar 8 2014, 4:48 PM

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?

Bastien Montagne (mont29) lowered the priority of this task from 90 to Normal.Mar 8 2014, 4:49 PM
• matali (mattali) added a comment.Mar 9 2014, 9:54 AM

@Bastien Montagne (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.

Campbell Barton (campbellbarton) added a comment.Mar 10 2014, 6:42 AM

@Bastien Montagne (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.
Campbell Barton (campbellbarton) added a comment.Mar 10 2014, 7:07 AM

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

Bastien Montagne (mont29) claimed this task.Mar 10 2014, 8:37 AM

@Campbell Barton (campbellbarton) 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…

• matali (mattali) added a comment.Apr 1 2014, 8:23 PM

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

Bastien Montagne (mont29) changed the task status from Unknown Status to Resolved.May 2 2014, 10:27 AM

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

Campbell Barton (campbellbarton) mentioned this in T42771: [Feature Request] Please fix the "Maya Settings".Dec 1 2014, 10:14 AM