Switching object in EditMode to invisible layer locks you out of ObjectMode #40526

New Issue

Mark · 2014-06-06T20:26:31+02:00

Mark commented

2014-06-06 20:26:31 +02:00

System Information
Debian Linux with Radeon HD 7470 graphics card

Blender Version
Broken:2.70a

Short description of error
If an object being editted is moved to a non-visible layer, the UI can no longer be switched from Edit Mode to Object Mode

Exact steps for others to reproduce the error
Take any .blend scene, even the initial cube.
Press 1 so only Layer 1 is visible
Select the cube object and TAB into Edit Mode.
In the Properties window select the Object Tab.
Within the Relations->Layers, switch the object to Layer 2, which is not visible.
You are now locked out of switching to Object Mode, either by pressing TAB or via the 2D view's object interaction pulldown.

To fix this, you must either switch the object BACK to a visible layer, or press a number key to make the object's layer visible.

Mark

**System Information** Debian Linux with Radeon HD 7470 graphics card **Blender Version** Broken:2.70a **Short description of error** If an object being editted is moved to a non-visible layer, the UI can no longer be switched from Edit Mode to Object Mode **Exact steps for others to reproduce the error** Take any .blend scene, even the initial cube. Press 1 so only Layer 1 is visible Select the cube object and TAB into Edit Mode. In the Properties window select the Object Tab. Within the Relations->Layers, switch the object to Layer 2, which is not visible. You are now locked out of switching to Object Mode, either by pressing TAB or via the 2D view's object interaction pulldown. To fix this, you must either switch the object BACK to a visible layer, or press a number key to make the object's layer visible. - Mark

Mark commented

2014-06-06 20:26:31 +02:00

Changed status to: 'Open'

Mark commented

2014-06-06 20:26:31 +02:00

Added subscriber: @cmuAdamson

blender-admin commented

2014-06-06 20:26:31 +02:00

#40700 was marked as duplicate of this issue

Kévin Dietrich commented

2014-06-07 04:10:04 +02:00

Added subscriber: @kevindietrich

Kévin Dietrich commented

2014-06-07 04:10:04 +02:00

Can confirm this behavior on Linux with latest head as well (918f6a4)

Can confirm this behavior on Linux with latest head as well (918f6a4)

Lukas Tönne commented

2014-06-07 08:10:58 +02:00

Added subscriber: @LukasTonne

Lukas Tönne commented

2014-06-07 08:10:58 +02:00

Confirmed.

There is a discrepancy in "object from context" functions used in the operators here:

The generic object.mode_set operator uses the context.active_object attribute. This attribute is defined in the View3D space by checking the active object's layers.
The operator's poll method, however, uses ED_object_active_context. This function retrieves the context.object attribute primarily, which is defined screen-wide without filtering by visible layers.

So while the poll method passes, the actual execution function quits early due to the filtering.

Confirmed. There is a discrepancy in "object from context" functions used in the operators here: * The generic object.mode_set operator uses the **context.active_object** attribute. This attribute is defined in the View3D space by checking the active object's layers. * The operator's `poll` method, however, uses `ED_object_active_context`. This function retrieves the **context.object** attribute primarily, which is defined screen-wide without filtering by visible layers. So while the poll method passes, the actual execution function quits early due to the filtering.

Lukas Tönne commented

2014-06-10 12:01:16 +02:00

Changed status from 'Open' to: 'Archived'

Lukas Tönne closed this issue

2014-06-10 12:01:16 +02:00

Lukas Tönne self-assigned this 2014-06-10 12:01:16 +02:00

Lukas Tönne commented

2014-06-10 12:01:16 +02:00

Added subscribers: @Sergey, @ideasman42

Lukas Tönne commented

2014-06-10 12:01:16 +02:00

Discussed with @ideasman42 and @Sergey on IRC. There are a few potential solutions, unfortunately none of them is really feasible:

Use ED_object_active_context consistently throughout mode switch operators. This would be the least radical solution, but the standard way of using active object is still via context.active_object. Changing each and every ocurrence is a major undertaking and hard to prevent the same bug in the future this way.
Change the operator context to SCREEN instead of AREA (view3d), because then the view3d filtering of active_object by layers would not happen. Unfortunately this can have unwanted side effects, particularly for things like localview and unlocked layers.
Not apply layer filtering to context.active_object in general. This would have even worse side effects, although it might be the correct behavior. There is no telling what would happen in all the hundreds of other use cases ...

So for now will put this bug on the ToDo list ...
http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Editors#3D_View

Discussed with @ideasman42 and @Sergey on IRC. There are a few potential solutions, unfortunately none of them is really feasible: - Use `ED_object_active_context` consistently throughout mode switch operators. This would be the least radical solution, but the standard way of using active object is still via context.active_object. Changing each and every ocurrence is a major undertaking and hard to prevent the same bug in the future this way. - Change the operator context to *SCREEN* instead of *AREA* (view3d), because then the view3d filtering of `active_object` by layers would not happen. Unfortunately this can have unwanted side effects, particularly for things like localview and unlocked layers. - Not apply layer filtering to `context.active_object` in general. This would have even worse side effects, although it might be the correct behavior. There is no telling what would happen in all the hundreds of other use cases ... So for now will put this bug on the ToDo list ... http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Editors#3D_View

Sergey Sharybin commented

2014-06-19 10:40:40 +02:00

Added subscriber: @ReeceRobinson