Skip to content
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

Closed
qgib opened this issue Jan 19, 2015 · 6 comments
Closed
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Forms

Comments

@qgib
Copy link
Contributor

qgib commented Jan 19, 2015

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

image

@qgib
Copy link
Contributor Author

qgib commented Jan 19, 2015

Author Name: Giovanni Manghi (@gioman)


  • category_id was changed from Vectors to Edit widget

@qgib
Copy link
Contributor Author

qgib commented May 9, 2015

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was changed from Version 2.8 to Version 2.8.2

@qgib
Copy link
Contributor Author

qgib commented May 14, 2015

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was changed from Version 2.8.2 to Version 2.10

@qgib
Copy link
Contributor Author

qgib commented Nov 7, 2015

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id removed Version 2.10

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 0
  • easy_fix was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Jan 29, 2018

Author Name: Nyall Dawson (@nyalldawson)


Not an issue on 3.0 master


  • resolution was changed from to fixed/implemented
  • description was changed from 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! 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!

  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Jan 29, 2018
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Forms labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Forms
Projects
None yet
Development

No branches or pull requests

1 participant