Some addons not respecting workspace filter #62567

New Issue

Vojtech Lacina · 2019-03-14T12:32:33+01:00

Vojtech Lacina commented

2019-03-14 12:32:33 +01:00

System Information
Operating system: WIndows 64bit CZ
Graphics card: nVidia 1080GT

Blender Version
Broken: 2.80, 2019-03-14 00:12, Hash: 87aca8bd02bc

Short description of error
Some Addons, installed in Blender, activated in Addon manager, NOT ACTIVATED in (specified) Workspace Addon Filter, behaves like they are active.
Their UI or key binding is active in Workspaces, where I didn't activate them on purpose, yet they are presented here.

Examples (I found to this point, there fer few more I can't remember now, only tried them once)
MACHIN3tools: https://gumroad.com/l/MACHIN3tools - Shortcuts
BoxCutter: https://gumroad.com/l/BoxCutter - UI icon in tools panel + Shortcuts
SpeedFlow: https://gumroad.com/l/speedflow - UI in viewport

Exact steps for others to reproduce the error
Install addon, activate it in Addon Manager in preferences, create new Workspace, turn on Addon Filter. Addon still presented

**System Information** Operating system: WIndows 64bit CZ Graphics card: nVidia 1080GT **Blender Version** Broken: 2.80, 2019-03-14 00:12, Hash: 87aca8bd02bc **Short description of error** Some Addons, installed in Blender, activated in Addon manager, NOT ACTIVATED in (specified) Workspace Addon Filter, behaves like they are active. Their UI or key binding is active in Workspaces, where I didn't activate them on purpose, yet they are presented here. Examples (I found to this point, there fer few more I can't remember now, only tried them once) MACHIN3tools: https://gumroad.com/l/MACHIN3tools - Shortcuts BoxCutter: https://gumroad.com/l/BoxCutter - UI icon in tools panel + Shortcuts SpeedFlow: https://gumroad.com/l/speedflow - UI in viewport **Exact steps for others to reproduce the error** Install addon, activate it in Addon Manager in preferences, create new Workspace, turn on Addon Filter. Addon still presented

Vojtech Lacina commented

2019-03-14 12:32:33 +01:00

Added subscriber: @v01tech

Sebastian Parborg commented

2019-03-14 13:21:42 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-03-14 13:21:42 +01:00

Changed status from 'Open' to: 'Archived'

Sebastian Parborg closed this issue

2019-03-14 13:21:42 +01:00

Sebastian Parborg self-assigned this 2019-03-14 13:21:42 +01:00

Sebastian Parborg commented

2019-03-14 13:21:42 +01:00

Thanks for the report, but these add-ons are not developed by Blender, please report the bug to the original authors.

If you can replicate this with an official addon, then that is something we can look at.

Thanks for the report, but these add-ons are not developed by Blender, please report the bug to the original authors. If you can replicate this with an official addon, then that is something we can look at.

Vojtech Lacina commented

2019-03-14 15:01:22 +01:00

Thanks for info. I asked Pablo on Twitter and he pointed me here, so I thought it's some kind of Blender functionality.

I'll report it to addon creators, sorry for unnecessary bugreport.

Thanks for info. I asked Pablo on Twitter and he pointed me here, so I thought it's some kind of Blender functionality. I'll report it to addon creators, sorry for unnecessary bugreport.

Sebastian Parborg commented

2019-03-14 15:45:23 +01:00

Don't get me wrong, this could be a problem with the blender API.
But we need either the issue to happen with an official addon or to have a very minimal code example that triggers the issue.

We can't provide support for any 3rd party addons.

Don't get me wrong, this could be a problem with the blender API. But we need either the issue to happen with an official addon or to have a very minimal code example that triggers the issue. We can't provide support for any 3rd party addons.

MACHIN3 commented

2019-03-14 15:47:10 +01:00

Added subscriber: @MACHIN3

MACHIN3 commented

2019-03-14 15:47:10 +01:00

Changed status from 'Archived' to: 'Open'

MACHIN3 reopened this issue

2019-03-14 15:47:10 +01:00

MACHIN3 commented

2019-03-14 15:47:10 +01:00

It's not a problem with the addons. To my knowledge, there is nothing an addon dev has to do, to work with this Blender feature. If there is something addons devs need to do, I'd appreciate a link to information.

You can replicate this problem with the Development Icon Viewer addon. Filter addons, leave it unchecked, its button remains in the python console bar.

Based on my tests, it seems the workspace filter seems to work great for disabling addon defined pie menus and panels. It fails for addon defined keymaps however.
Is there an official addon that sets a keymap item? I'm not aware of one.

It's not a problem with the addons. To my knowledge, there is nothing an addon dev has to do, to work with this Blender feature. If there is something addons devs need to do, I'd appreciate a link to information. You can replicate this problem with the Development Icon Viewer addon. Filter addons, leave it unchecked, its button remains in the python console bar. Based on my tests, it seems the workspace filter seems to work great for disabling addon defined pie menus and panels. It fails for addon defined keymaps however. Is there an official addon that sets a keymap item? I'm not aware of one.

Sebastian Parborg removed their assignment 2019-03-14 15:58:47 +01:00

Campbell Barton was assigned by Sebastian Parborg

2019-03-14 15:58:47 +01:00

Sebastian Parborg commented

2019-03-14 15:58:47 +01:00

Added subscriber: @ideasman42

Sebastian Parborg commented

2019-03-14 15:58:47 +01:00

@ideasman42 bug or not?

Ted Milker commented

2019-09-10 20:17:55 +02:00

Added subscribers: @brecht, @Teds

Ted Milker commented

2019-09-10 20:17:55 +02:00

@MACHIN3 The included Blender add-on F2 sets a keymap entry of F to mesh.f2. Node Wrangler also creates numerous entries in the keymap. These are not filtered out when Workspace Filter Add-ons is enabled but the add-ons are not checked, as far as I can tell.

Currently Workspace->Filter Add-ons does not filter keymap entries but I think it should. This would open up a lot of possibilities for add-on specific workspaces and using the same hotkeys. Personally, it would let me use Q for multiple add-ons that have similar workflows but different functionality(like BoxCutter/HardOps vs Speedflow). Right now, I have to find and use a limited number of unused letters under the hand on the keyboard or manually turn add-ons on and off when they're needed. Please @ideasman42 / @brecht have someone give this feature just a little more love to really unlock its full potential.

@MACHIN3 The included Blender add-on F2 sets a keymap entry of F to mesh.f2. Node Wrangler also creates numerous entries in the keymap. These are not filtered out when Workspace Filter Add-ons is enabled but the add-ons are not checked, as far as I can tell. Currently Workspace->Filter Add-ons does not filter keymap entries but I think it should. This would open up a lot of possibilities for add-on specific workspaces and using the same hotkeys. Personally, it would let me use Q for multiple add-ons that have similar workflows but different functionality(like BoxCutter/HardOps vs Speedflow). Right now, I have to find and use a limited number of unused letters under the hand on the keyboard or manually turn add-ons on and off when they're needed. Please @ideasman42 / @brecht have someone give this feature just a little more love to really unlock its full potential.

Vojtech Lacina commented

2019-11-22 17:45:03 +01:00

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: blender/blender@26bd5ebd42

Tried new official Blender build and this problem is still happening - addons, or their parts like shortcuts, icons and viewport gizoms are appearing in Workspaces, where they are not turned on.

Hele for example SpeedFlow https://gumroad.com/l/speedflow

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: `blender/blender@26bd5ebd42` Tried new official Blender build and this problem is still happening - addons, or their parts like shortcuts, icons and viewport gizoms are appearing in Workspaces, where they are not turned on. Hele for example SpeedFlow https://gumroad.com/l/speedflow ![obrazek.png](https://archive.blender.org/developer/F8155802/obrazek.png)

Campbell Barton was unassigned by Dalai Felinto

2019-12-23 16:34:54 +01:00

Brendon Murphy commented

2020-02-09 04:58:14 +01:00

Added subscriber: @BrendonMurphy

Brendon Murphy commented

2020-02-09 04:58:14 +01:00

hi, I had this error/bug/usability concern... myself in the viewport pies addon.
I found the issue was in the submodule registration.
Basically, the workspace filter filters active addons but not the addon's submodules if they are not correctly enabled/activated and most important, registered.. This was especially transparent in the viewport pies addon where the behavior was to activate the addon then activate each pie individually. After I adopted the submodule code from the "official pies" 2.8? I was able to use the viewport pies and they respected the workspace filters properly. You can see the submodule code in the viewport pies here: https://developer.blender.org/diffusion/BA/browse/master/space_view3d_pie_menus/init.py hope it helps.
Unfortunately this is not really a bug and relates to 3rd party addons. Whilst this is a known issue and my initial discovery of the bug was using hardops.. I'm not sure what's expected here.
Register your addons and submodules properly and workspace filtering works.
Thanks.

hi, I had this error/bug/usability concern... myself in the viewport pies addon. I found the issue was in the submodule registration. Basically, the workspace filter filters active addons but not the addon's submodules if they are not correctly enabled/activated and most important, registered.. This was especially transparent in the viewport pies addon where the behavior was to activate the addon then activate each pie individually. After I adopted the submodule code from the "official pies" 2.8? I was able to use the viewport pies and they respected the workspace filters properly. You can see the submodule code in the viewport pies here: https://developer.blender.org/diffusion/BA/browse/master/space_view3d_pie_menus/__init__.py hope it helps. Unfortunately this is not really a bug and relates to 3rd party addons. Whilst this is a known issue and my initial discovery of the bug was using hardops.. I'm not sure what's expected here. Register your addons and submodules properly and workspace filtering works. Thanks.

Sign in to join this conversation.