Scene not changed when use Python in Pinned workspace #100165

New Issue

Antonio Vazquez · 2022-08-03T11:39:53+02:00

Antonio Vazquez commented

2022-08-03 11:39:53 +02:00

Failed: Version 3.3.0 Beta 31/07/2022
Worked: Never, PIN is a new option in 3.3 version.

Using the add-on we have developed for storyboarding, when the scene is pinned to the workspace, the scene is not correct when is changed using python.

WorkspacePinned.mp4

The python code is very simple:

context.window.workspace = storypencil_main_workspace

Failed: Version 3.3.0 Beta 31/07/2022 Worked: Never, PIN is a new option in 3.3 version. Using the add-on we have developed for storyboarding, when the scene is pinned to the workspace, the scene is not correct when is changed using python. [WorkspacePinned.mp4](https://archive.blender.org/developer/F13333457/WorkspacePinned.mp4) The python code is very simple: ``` context.window.workspace = storypencil_main_workspace ```

Antonio Vazquez commented

2022-08-03 11:39:53 +02:00

Added subscriber: @antoniov

Antonio Vazquez commented

2022-08-03 11:40:26 +02:00

Added subscribers: @JulianEisel, @mendio

Omar Emara commented

2022-08-03 13:40:59 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-08-03 13:40:59 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Omar Emara commented

2022-08-03 13:40:59 +02:00

I can't seem to replicate this myself. Does the target Workspace have a different pinned scene than 03_Scene?
I am testing with this file:

pinnedWorkspace.blend

What does this mean?

Worked: New function of this version

I can't seem to replicate this myself. Does the target Workspace have a different pinned scene than `03_Scene`? I am testing with this file: [pinnedWorkspace.blend](https://archive.blender.org/developer/F13333623/pinnedWorkspace.blend) What does this mean? > Worked: New function of this version

Omar Emara commented

2022-08-17 11:44:55 +02:00

Are you able to reproduce the issue on the attached file? Because I can't seem to be able to.

Antonio Vazquez commented

2022-08-18 16:51:49 +02:00

No, I cannot...I guess this is related to some multi thread issue and depends on the file size and complexity and CPU speed.... a really hard bug to catch.

Omar Emara commented

2022-08-18 16:56:01 +02:00

Could you share the file where you originally reproduced the bug?

Antonio Vazquez commented

2022-08-25 16:39:57 +02:00

I'm doing some debug and I have seen something weird.

My python code does this: context.window.workspace = scene.storypencil_edit_workspace

After that line, both variables would contain the same, I mean, the right variable is a workspace and is assigned to the context.workspace, but doing a debug I can see the left variable is not updated as you can see in the image below stopped in the next line after the assign of the value.

Is this normal? the question is why the variable is not updated because the code is working when is not pinned, so that means that the context.window.workspace update is delayed.

How can I force to update that value?

I'm doing some debug and I have seen something weird. My python code does this: ` context.window.workspace = scene.storypencil_edit_workspace` After that line, both variables would contain the same, I mean, the right variable is a workspace and is assigned to the `context.workspace`, but doing a debug I can see the left variable is not updated as you can see in the image below stopped in the next line after the assign of the value. ![image.png](https://archive.blender.org/developer/F13416854/image.png) Is this normal? the question is why the variable is not updated because the code is working when is not pinned, so that means that the `context.window.workspace` update is delayed. How can I force to update that value?

Maurits Valk commented

2022-08-28 06:13:20 +02:00

Added subscriber: @storyvalk

Omar Emara commented

2022-08-29 09:33:38 +02:00

It seems this is normal. Changing the workspace is a change of context, so it is intentionally delayed until all code that depends on the current context is executed.
This is done by adding a ND_WORKSPACE_SET notifier to the window, which is handled in wm_event_do_notifiers, which execute automatically as part of the main loop and can't be invoked manually as far as I can see.
So you can't force an update to that value. Why do you need it to take effect immediately?

It seems this is normal. Changing the workspace is a change of context, so it is intentionally delayed until all code that depends on the current context is executed. This is done by adding a `ND_WORKSPACE_SET` notifier to the window, which is handled in `wm_event_do_notifiers`, which execute automatically as part of the main loop and can't be invoked manually as far as I can see. So you can't force an update to that value. Why do you need it to take effect immediately?

Julian Eisel commented

2022-08-29 10:38:44 +02:00

About that, see D15614: Py Docs: Document delayed setting of UI data.

About that, see [D15614: Py Docs: Document delayed setting of UI data](https://archive.blender.org/developer/D15614).

Antonio Vazquez commented

2022-08-29 10:48:10 +02:00

@OmarEmaraDev I need the instant update because the add-on is switching all the time back and forth between VSE scene and strip scene to draw the storyboard.... I will investigate alternatives. Anyway, it would be great to have a context.windows.workspace.update()for this type of situations as we have for view_layers. I know that force the update is not the best, but in situations like this could be the best solution.

@OmarEmaraDev I need the instant update because the add-on is switching all the time back and forth between VSE scene and strip scene to draw the storyboard.... I will investigate alternatives. Anyway, it would be great to have a `context.windows.workspace.update()`for this type of situations as we have for `view_layers`. I know that force the update is not the best, but in situations like this could be the best solution.

Julian Eisel commented

2022-08-29 10:57:49 +02:00

The situation is a bit different for view layers. For them the update is just delayed for performance reasons. So enforcing an immediate update is fine. For workspaces (and other UI changes) it's delayed because it could corrupt context. IIRC switching workspaces immediately will just result in crashes in many cases.

Omar Emara commented

2022-08-29 11:03:36 +02:00

Since this is getting documented as Julian pointed out, I would say this is handled.
But is the original issue you pointed out a manifestation of the issue you just described? Or is it different?

Since this is getting documented as Julian pointed out, I would say this is handled. But is the original issue you pointed out a manifestation of the issue you just described? Or is it different?

Antonio Vazquez commented

2022-08-29 12:15:00 +02:00

I all agree, we could consider this a Known Issue

I all agree, we could consider this a `Known Issue`

Omar Emara commented

2022-08-29 12:21:18 +02:00

Changed status from 'Needs User Info' to: 'Archived'

Omar Emara closed this issue

2022-08-29 12:21:18 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Scene not changed when use Python in Pinned workspace #100165