Search Issue Tracker

Fixed

Fixed in 2022.3.14f1, 2023.2.0b18, 2023.3.0a8

Votes

0

Found in

2022.3.7f1

2023.1.8f1

2023.2.0b4

2023.3.0a5

Issue ID

UUM-45813

Regression

Yes

Scene view pan is not ignored when using custom tools with popup menus

--

-

Reproduction steps:
1. Open the attached project “ContextMenuIssue”
2. Open the “Assets/SelectionUtility/Sample/SelectionUtilitySample” Scene
3. In the Scene view right click on any element and move the cursor around

Expected result: A custom context menu is opened and the Scene view stays in place when moving the cursor around
Actual result: A custom context menu is opened but the Scene view is panned when moving the cursor

Reproducible with: 2022.2.0a13. 2022.3.7f1, 2023.1.8f1, 2023.2.0b4
Not reproducible with: 2021.3.29f1, 2022.2.0a12

Reproducible on: macOS 13.1.4 (c)

  1. Resolution Note (fix version 2023.3.0a8):

    Thank you for reporting this issue. It has been fixed. Your solution should work without any changes needed.
    However, it is also possible to use the new context menu in the Scene view. You can register menu items for specific components by using the MenuItem attribute and the "CONTEXT/" prefix. These menu items will be added to the context menu in the Scene view and will appear when the current selection has the components in question. For example, [MenuItem("CONTEXT/Rigidbody/My custom action")].
    Another alternative to your solution would be to use Shortcuts. It is now possible to allocate the same mouse button, in your case Mouse1, to multiple shortcuts as long as the context is different.

  2. Resolution Note (fix version 2023.2.0b18):

    Thank you for reporting this issue. It has been fixed. Your solution should work without any changes needed.
    However, it is also possible to use the new context menu in the Scene view. You can register menu items for specific components by using the MenuItem attribute and the "CONTEXT/" prefix. These menu items will be added to the context menu in the Scene view and will appear when the current selection has the components in question. For example, [MenuItem("CONTEXT/Rigidbody/My custom action")].
    Another alternative to your solution would be to use Shortcuts. It is now possible to allocate the same mouse button, in your case Mouse1, to multiple shortcuts as long as the context is different.

  3. Resolution Note (fix version 2022.3.14f1):

    Thank you for reporting this issue. It has been fixed.
    Another solution would be to use Shortcuts. It is now possible to allocate the same mouse button, in your case Mouse1, to multiple shortcuts as long as the context is different.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.