Collection Manager Addon doesn't work in Local View mode #74931

Closed
opened 2020-03-19 17:42:11 +01:00 by Christoph Werner · 7 comments

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

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: blender/blender@375c7dc4ca
Worked: (optional)

Addon Information
Name: Collection Manager (1, 8, 9)
Author: Ryan Inch

Short description of error
Moving an object to another Collection in "Local view mode" doesn't work and result in an error.

Displayed error:

Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\object_collection_manager\operators.py", line 161, in invoke
    bpy.ops.object.move_to_collection(collection_index=self.collection_index)
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py", line 201, in __call__
    ret = op_call(self.idname_py(), None, kw)
RuntimeError: Operator bpy.ops.object.move_to_collection.poll() failed, context is incorrect

location: <unknown location>:-1

location: <unknown location>:-1
Error: Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\object_collection_manager\operators.py", line 161, in invoke
    bpy.ops.object.move_to_collection(collection_index=self.collection_index)
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py", line 201, in __call__
    ret = op_call(self.idname_py(), None, kw)
RuntimeError: Operator bpy.ops.object.move_to_collection.poll() failed, context is incorrect

location: <unknown location>:-1

Exact steps for others to reproduce the error

  1. Select an object
  2. In 3D Viewport use the View menu->Local View->Toggle local view
  3. Press M-key to move the active object to a different Collection
  • Results in the error above

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: `blender/blender@375c7dc4ca` Worked: (optional) **Addon Information** Name: Collection Manager (1, 8, 9) Author: Ryan Inch **Short description of error** Moving an object to another Collection in "Local view mode" doesn't work and result in an error. Displayed error: ``` Traceback (most recent call last): File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\object_collection_manager\operators.py", line 161, in invoke bpy.ops.object.move_to_collection(collection_index=self.collection_index) File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py", line 201, in __call__ ret = op_call(self.idname_py(), None, kw) RuntimeError: Operator bpy.ops.object.move_to_collection.poll() failed, context is incorrect location: <unknown location>:-1 location: <unknown location>:-1 Error: Traceback (most recent call last): File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\object_collection_manager\operators.py", line 161, in invoke bpy.ops.object.move_to_collection(collection_index=self.collection_index) File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py", line 201, in __call__ ret = op_call(self.idname_py(), None, kw) RuntimeError: Operator bpy.ops.object.move_to_collection.poll() failed, context is incorrect location: <unknown location>:-1 ``` **Exact steps for others to reproduce the error** 1. Select an object 2. In 3D Viewport use the View menu->Local View->Toggle local view 3. Press M-key to move the active object to a different Collection - > Results in the error above

Added subscriber: @ChristophWerner

Added subscriber: @ChristophWerner
Ryan Inch self-assigned this 2020-04-08 05:57:32 +02:00
Member

Changed status from 'Needs Triage' to: 'Resolved'

Changed status from 'Needs Triage' to: 'Resolved'
Member

@ChristophWerner Apologies, for getting back to you so late, I didn't see this until today. Quite by accident this was just fixed a couple days ago. So thanks for the bug report, and you can either grab a daily build or go to #69577 and download the zip for 2.83+ for the fix.

@ChristophWerner Apologies, for getting back to you so late, I didn't see this until today. Quite by accident this was just fixed a couple days ago. So thanks for the bug report, and you can either grab a daily build or go to #69577 and download the zip for 2.83+ for the fix.

Thank you. It works.
Can I copy the new version to the 2.82 folder, too?

Does it work with v2.82? I'm using the current master.

Thank you. It works. Can I copy the new version to the 2.82 folder, too? Does it work with v2.82? I'm using the current master.
Member

Yes, you can copy the new version into the 2.82 folder; it should work fine.

Yes, you can copy the new version into the 2.82 folder; it should work fine.

In #74931#905940, @Imaginer wrote:
Yes, you can copy the new version into the 2.82 folder; it should work fine.

Thank you. All is fine.

> In #74931#905940, @Imaginer wrote: > Yes, you can copy the new version into the 2.82 folder; it should work fine. Thank you. All is fine.
Member

Great! No problem.

Great! No problem.
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#74931
No description provided.