-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
multiple Feature Attributes forms can be opened for the same feature when Identified #21564
Comments
Author Name: Anita Graser (@anitagraser) -1 for modal because it's unnecessarily restrictive +1 for only one window per feature |
Author Name: Harrissou Santanna (@DelazJ) Anita Graser wrote:
Totally agree (no modal and only one form)! |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Jürgen Fischer (@jef-n) Fixed in changeset "20197c2fa31e454b095be6b68771274ec5540c39".
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Steven Mizuno (Steven Mizuno)
Original Redmine Issue: 13520
Affected QGIS version: master
Redmine category:map_tools
Multiple Feature Attributes forms can be opened for the same feature when "Auto open form" is checked and you click multiple times on one feature or if you do View feature form multiple times on an item in Identify Results. This can be confusing when many such forms are opened, and it can lead to loss of data when editing a layer.
Examples: which form for a given feature was changed? or make changes in different forms of a given feature -- which one wins?.
As the form windows are top-level windows they may be obscured by the QGIS main window which can be even more confusing. There is a clue that forms are still open as the highlight is drawn one for each form. And the windows are shown in the task bar as well.
I believe the Features Attributes form should be application modal, or at the very least, create only one window per feature and then put focus on that window on subsequent clicking on a feature.
This is somewhat related to #21512
Related issue(s): #21512 (relates)
Redmine related issue(s): 13465
The text was updated successfully, but these errors were encountered: