Object Scatter doesnt show up in operator search #76256

Closed
opened 2020-04-30 10:52:18 +02:00 by Rahul Chaudhary · 7 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5100

Blender Version
Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-04-29 19:38, hash: blender/blender@00e0034b13
Worked: 2.83 (sub 15), branch: master, commit date: 2020-04-29 19:35, hash: blender/blender@cd833d8879

The built in add-on object scatter doesn't show up in operator search, enabling and disabling the addon throws some errors on the system console/terminal.

System_console.txt

Exact steps for others to reproduce the error

  1. Enable Scatter add-on
  2. Select an object
  3. Open operator search menu
  4. Type scatter

Works with default blend file

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5100 **Blender Version** Broken: version: 2.90 (sub 0), branch: master, commit date: 2020-04-29 19:38, hash: `blender/blender@00e0034b13` Worked: 2.83 (sub 15), branch: master, commit date: 2020-04-29 19:35, hash: `blender/blender@cd833d8879` The built in add-on object scatter doesn't show up in operator search, enabling and disabling the addon throws some errors on the system console/terminal. [System_console.txt](https://archive.blender.org/developer/F8502720/System_console.txt) **Exact steps for others to reproduce the error** 1. Enable Scatter add-on 2. Select an object 3. Open operator search menu 4. Type scatter Works with default blend file

Added subscriber: @RC12

Added subscriber: @RC12
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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

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

Regarding search: It is a bit of an obscure situation atm...

Since the new F3 Menu search, Operator search is only accessible through the Edit menu in the topbar [if you have Developer Extras enabled in Preferences].
But that doesnt provide the right context for many operators (polling for 3DView for example).
So I think to get there, you have to do a combination of the two search menus

In blender/blender#74157#918414, @lichtwerk wrote:
I hope this hasnt been mentioned already (if so: sorry for the duplicate...), and maybe I am missing something, but following scenario seems pretty strange to me:

  • As an Addon developer while prototyping I dont add operators to menus [so I have to use Operator Search]
  • My operator relys on SPACE_VIEW3D context
  • Operator Search is accessible through the topbar [thus polling SPACE_VIEW3D context will fail if I launch my operator from Operator Search]

What is the intended way to do this now?

  • Should I be searching Operator Search in the 3DView Menu Search and then look for my operator there?
  • Or should I add Operator Search to Quick Favorites to be able to have SPACE_VIEW3D context?

That being said, developers are aware to some extend, we have other reports open for this:
blender/blender#74157 (Use menus for operator search & various improvements)
blender/blender#76227 (Make All Operators Accessible from Menus)

Regarding search, I'll drop a note in blender/blender#76227 that this needs to be done for supported Addons as well (but otherwise I think discussion about search should be continued in these reports...)

enabling and disabling the addon throws some errors on the system console/terminal.

Cannot reproduce... What are these errors? (will leave the report open for this issue)

Regarding search: It is a bit of an obscure situation atm... Since the new F3 Menu search, `Operator search` is only accessible through the `Edit` menu in the topbar [if you have `Developer Extras` enabled in `Preferences`]. But that doesnt provide the right context for many operators (polling for 3DView for example). So I think to get there, you have to do a combination of the two search menus > In blender/blender#74157#918414, @lichtwerk wrote: > I hope this hasnt been mentioned already (if so: sorry for the duplicate...), and maybe I am missing something, but following scenario seems pretty strange to me: > - As an Addon developer while prototyping I dont add operators to menus [so I have to use `Operator Search`] > - My operator relys on `SPACE_VIEW3D` context > - `Operator Search` is accessible through the topbar [thus polling `SPACE_VIEW3D` context will fail if I launch my operator from `Operator Search`] > > What is the intended way to do this now? > - Should I be searching `Operator Search` in the 3DView `Menu Search` and then look for my operator there? > - Or should I add `Operator Search` to Quick Favorites to be able to have `SPACE_VIEW3D` context? That being said, developers are aware to some extend, we have other reports open for this: blender/blender#74157 (Use menus for operator search & various improvements) blender/blender#76227 (Make All Operators Accessible from Menus) Regarding search, I'll drop a note in blender/blender#76227 that this needs to be done for supported Addons as well (but otherwise I think discussion about search should be continued in these reports...) > enabling and disabling the addon throws some errors on the system console/terminal. Cannot reproduce... What are these errors? (will leave the report open for this issue)

Checked again and the errors doesnt seem to be related to the add-on and is fixed in the latest build. It only appears on an older build of 2.9 when add-on preferences is opened. Having the operator search on quick favorite fixes the issue with search operator.

Checked again and the errors doesnt seem to be related to the add-on and is fixed in the latest build. It only appears on an older build of 2.9 when add-on preferences is opened. Having the operator search on quick favorite fixes the issue with search operator.
Member

OK, thx getting back.

If the error is gone though, I think we should close this (and continue discussion about search in blender/blender#76227, blender/blender#74157)...

OK, thx getting back. If the error is gone though, I think we should close this (and continue discussion about search in blender/blender#76227, blender/blender#74157)...
Member

Closed as duplicate of blender/blender#76227

Closed as duplicate of blender/blender#76227
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#76256
No description provided.