-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
snapping advanced configuration does not show snapping dialog #24498
Comments
Author Name: Regis Haubourg (@haubourg)
|
Author Name: Denis Rouzaud (@3nids) enabling the advanced mode from the toolbar is not meant to show the dialog or the dock. You have to use project menu -> snapping settings to show the dialog.
|
Author Name: Regis Haubourg (@haubourg) ok, I get it, the entry has been moved from settings to project menu. Now that we have a ditigizing toolbar and dock panel, I'd vote in favour to remove the old dialog option. It is a bit weird to have a dynamic and easy to use toolbar and have to 5 clics from a menu to change snapping options. What about having a way to show / hide the dock when activating the snapping toolbar? |
Author Name: Tobias Wendorff (Tobias Wendorff) I also was confused about "dialog" and "dock". It's still in dev. Also, the new snapping toolbar is hidden in menu item "project". Took a while to find it. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Regis Haubourg (@haubourg)
Original Redmine Issue: 16596
Affected QGIS version: master
Redmine category:digitising
Assignee: Denis Rouzaud
In qgis 2.99, when the digitizing snapping option is set to "dialog" and not "dock", the dialog does not show up when selecting the advanced configuration from the toolbar dropdown widget. In this setting, it's not possible to set snapping options, so it's a regression.
When set to "dock", it's possible to open the dock but it doesn't show up itself. It would be good to the dock opens/close when activating/deactivating the toolbar too. This is more a UX issue.
The text was updated successfully, but these errors were encountered: