You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugFunctionality which is not working as intendedduplicateThis issue or pull request already existstodeleteIssues which will be deleted as part of periodic cleanupwallsIssues related to Walls and their configuration
Double-clicking the line segment part of walls no longer allows you to edit the walls. Instead, you have to click one of the Wall's two end-points to open the Wall Configuration dialog.
What ways of accessing Foundry can you encounter this issue in?
Native App (Electron)
Chrome
Firefox
Safari
Other
Reproduction Steps
Enable the Select Walls tool
Double-click the line segment portion of a Wall
Current: Nothing happens other than controlling the Wall
Preferred: The Wall is controlled and the Configure Wall dialog displays for that Wall
What core version are you reporting this for?
12.322
Relevant log output
No response
Bug Checklist
The issue occurs while all Modules are disabled
The text was updated successfully, but these errors were encountered:
Norc
added
the
bug
Functionality which is not working as intended
label
May 10, 2024
bugFunctionality which is not working as intendedduplicateThis issue or pull request already existstodeleteIssues which will be deleted as part of periodic cleanupwallsIssues related to Walls and their configuration
What happened?
Double-clicking the line segment part of walls no longer allows you to edit the walls. Instead, you have to click one of the Wall's two end-points to open the Wall Configuration dialog.
What ways of accessing Foundry can you encounter this issue in?
Reproduction Steps
Current: Nothing happens other than controlling the Wall
Preferred: The Wall is controlled and the Configure Wall dialog displays for that Wall
What core version are you reporting this for?
12.322
Relevant log output
No response
Bug Checklist
The text was updated successfully, but these errors were encountered: