-
-
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
Value map table gets corrupted after chaging the edit widget to another one #20209
Comments
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Nyall Dawson (@nyalldawson) Not an issue on 3.0 master
Since then the user can apparently unselected the value map widget, and then select it again and see the previously created table, but instead the table is filled with strange things, see attached image !https://dl.dropboxusercontent.com/s/f78btqyojq5ydph/comp2.png! to Until 2.2 if a user used a value map and then unselected this widget to use another, the value map table got lost, so in case the value map widget was selected again it was necessary to create/import it again. Not very handy, but it was a known behavior. Since then the user can apparently unselected the value map widget, and then select it again and see the previously created table, but instead the table is filled with strange things, see attached image !https://dl.dropboxusercontent.com/s/f78btqyojq5ydph/comp2.png!
|
Author Name: Giovanni Manghi (@gioman)
Original Redmine Issue: 12006
Affected QGIS version: master
Redmine category:edit_widget
Until 2.2 if a user used a value map and then unselected this widget to use another, the value map table got lost, so in case the value map widget was selected again it was necessary to create/import it again. Not very handy, but it was a known behavior.
Since then the user can apparently unselected the value map widget, and then select it again and see the previously created table, but instead the table is filled with strange things, see attached image
The text was updated successfully, but these errors were encountered: