Top menu bar items not accessible with Python #59744

New Issue

Rombout Versluijs · 2018-12-22T04:28:29+01:00

Rombout Versluijs commented

2018-12-22 04:28:29 +01:00

System Information
OSX 10.11.6
Intel Irs Pro 1536

Blender Version
2.80 2018-12-19 #a91886e76ebd

Though is not really a bug i do want to add attention to this. A lot of items in the top bar are not or not properly accessible with Python.

For pre Blender 2.80 i have made 2 addons which allow me to switch render engines real quick using a shortcut. This part still works in 2.80 but other items like render and show render do not. When i use render image from the top menu, a new window opens (according to preset) and render is shown. Yet when i use my addon with the same code this does not happen. The image renders but not new window is opened.

When i use the same python code ops to show the render i get this error

Writing userprefs: '/Users/romboutversluijs/Library/Application Support/Blender/2.80/config/userpref.blend' ok
ERROR (wm.operator): /Users/fsiddi/bin/buildbot-worker/mac_x86_64_10_9_cmake/blender.git/source/blender/windowmanager/intern/wm_event_system.c:1345 wm_operator_invoke: invalid operator call 'RENDER_OT_view_show'

I also made an addon which allow me to use shorts cmd+1-9 to quick switch between now called workspaces, prior Screen Layout. I have been search high and low in the code but i can not find any info what python is used to activate each workspace. Could there be info added or make this accessible with python?

I do get the names, but there are some nameless leftovers in the code i guess. I an earlier version i had to default.00 something showing there and with the build from the 19th there is now 1 left.

To get the screens i used the same function as in bl 2.79 and earlier. Though it does get the names, it seems to be missing something

def avail_screens(self,context):
'''
enumerates available screen layouts and adding more items:
Maximize Area - will toggle current area to maximum window size
User Preferences - opens User Preferences window
'''
screen = bpy.data.screens
screens = [ ("User Preferences", "User Preferences", "User Preferences")
] # (identifier, name, description) optionally: (.., icon name, unique number)

for screen in bpy.data.screens:
screens.append((screen.name, screen.name, screen.name))
return screens

**System Information** OSX 10.11.6 Intel Irs Pro 1536 **Blender Version** 2.80 2018-12-19 #a91886e76ebd Though is not really a bug i do want to add attention to this. A lot of items in the top bar are not or not properly accessible with Python. For pre Blender 2.80 i have made 2 addons which allow me to switch render engines real quick using a shortcut. This part still works in 2.80 but other items like render and show render do not. When i use render image from the top menu, a new window opens (according to preset) and render is shown. Yet when i use my addon with the same code this does not happen. The image renders but not new window is opened. ![Screen Shot 2018-12-21 at 23.16.01.png](https://archive.blender.org/developer/F6031210/Screen_Shot_2018-12-21_at_23.16.01.png) When i use the same python code ops to show the render i get this error > Writing userprefs: '/Users/romboutversluijs/Library/Application Support/Blender/2.80/config/userpref.blend' ok > ERROR (wm.operator): /Users/fsiddi/bin/buildbot-worker/mac_x86_64_10_9_cmake/blender.git/source/blender/windowmanager/intern/wm_event_system.c:1345 wm_operator_invoke: invalid operator call 'RENDER_OT_view_show' > I also made an addon which allow me to use shorts cmd+1-9 to quick switch between now called workspaces, prior Screen Layout. I have been search high and low in the code but i can not find any info what python is used to activate each workspace. Could there be info added or make this accessible with python? I do get the names, but there are some nameless leftovers in the code i guess. I an earlier version i had to default.00 something showing there and with the build from the 19th there is now 1 left. ![Screen Shot 2018-12-21 at 23.25.17.png](https://archive.blender.org/developer/F6031221/Screen_Shot_2018-12-21_at_23.25.17.png) To get the screens i used the same function as in bl 2.79 and earlier. Though it does get the names, it seems to be missing something > def avail_screens(self,context): > ''' > enumerates available screen layouts and adding more items: > Maximize Area - will toggle current area to maximum window size > User Preferences - opens User Preferences window > ''' > screen = bpy.data.screens > screens = [ ("User Preferences", "User Preferences", "User Preferences") > ] # (identifier, name, description) optionally: (.., icon name, unique number) > > for screen in bpy.data.screens: > screens.append((screen.name, screen.name, screen.name)) > return screens

Rombout Versluijs commented

2018-12-22 04:28:29 +01:00

Added subscriber: @RomboutVersluijs

Rombout Versluijs commented

2018-12-22 06:02:14 +01:00

After doing more seaches i found this thread on BA, https://blenderartists.org/t/access-to-workspace-areas/1137024/4

It didnt work but i kept trying. Im now able to switch again using the popup menu and adding shortcuts using this line;

bpy.context.window.workspace = bpy.data.workspaces[self.layoutItems1]

It would help if the top menu bar showed Python info though. It seems this is one of the few sections which does not or hardly show any info

After doing more seaches i found this thread on BA, https://blenderartists.org/t/access-to-workspace-areas/1137024/4 It didnt work but i kept trying. Im now able to switch again using the popup menu and adding shortcuts using this line; > bpy.context.window.workspace = bpy.data.workspaces[self.layoutItems1] It would help if the top menu bar showed Python info though. It seems this is one of the few sections which does not or hardly show any info

Brecht Van Lommel commented

2018-12-24 00:23:03 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2018-12-24 00:23:03 +01:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2018-12-24 00:23:03 +01:00

Brecht Van Lommel self-assigned this 2018-12-24 00:23:03 +01:00

Brecht Van Lommel commented

2018-12-24 00:23:03 +01:00

For the first issue, please try asking on support forums or devtalk first. If you provide no exact steps for developers to reproduce the issue, it's not a bug to be investigated.

Rombout Versluijs commented

2018-12-24 03:59:48 +01:00

That why i stated it technically not a bug. But adding this to a forum will not get proper feedback. The Top bar acts different in a couple ways.

Using the view render command from the 3d viewport for instance. It give this error.

Traceback (most recent call last):
  File "/Applications/blender-2.80.0-git20181222.f1f8859ad52b-x86_64/blender.app/Contents/Resources/2.80/scripts/modules/addon_utils.py", line 377, in enable
    raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")
Exception: Add-on 'io_import_scene_lwo' has not been upgraded to 2.8, ignoring
ERROR (wm.operator): /Users/fsiddi/bin/buildbot-worker/mac_x86_64_10_9_cmake/blender.git/source/blender/windowmanager/intern/wm_event_system.c:1345 wm_operator_invoke: invalid operator call 'RENDER_OT_view_show'

The workspace tabs dont show any python info as do many other menu items. This is probably due to the new right click options we have.

That why i stated it technically not a bug. But adding this to a forum will not get proper feedback. The Top bar acts different in a couple ways. Using the view render command from the 3d viewport for instance. It give this error. ``` Traceback (most recent call last): File "/Applications/blender-2.80.0-git20181222.f1f8859ad52b-x86_64/blender.app/Contents/Resources/2.80/scripts/modules/addon_utils.py", line 377, in enable raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring") Exception: Add-on 'io_import_scene_lwo' has not been upgraded to 2.8, ignoring ERROR (wm.operator): /Users/fsiddi/bin/buildbot-worker/mac_x86_64_10_9_cmake/blender.git/source/blender/windowmanager/intern/wm_event_system.c:1345 wm_operator_invoke: invalid operator call 'RENDER_OT_view_show' ``` The workspace tabs dont show any python info as do many other menu items. This is probably due to the new right click options we have.

Brecht Van Lommel commented

2018-12-24 09:42:06 +01:00

If you want the show render thing to be investigated as a bug, you need to provide exact steps to reproduce it. For example by providing a simple example script and instructions on how to run it.

The workspace tabs not showing python info is not a bug.

If you want the show render thing to be investigated as a bug, you need to provide exact steps to reproduce it. For example by providing a simple example script and instructions on how to run it. The workspace tabs not showing python info is not a bug.

Rombout Versluijs commented

2018-12-25 02:08:11 +01:00

Okay done, https://developer.blender.org/T59832

Rombout Versluijs commented

2018-12-25 02:08:42 +01:00

PS is there a reason why top menu doesnt show Python info?

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

Top menu bar items not accessible with Python #59744