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

Relation reference widget - filter lists are not refreshed in attribute table form view #24309

Closed
qgib opened this issue Mar 30, 2017 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Forms High Priority
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Mar 30, 2017

Author Name: Regis Haubourg (@haubourg)
Original Redmine Issue: 16400
Affected QGIS version: 2.18.3
Redmine category:edit_widget
Assignee: Matthias Kuhn


When opening a standalone form, if chained filters were chosen, they are remembered and displayed correctly.
In attribute form view, when switching from one form to another, the filters are not refreshed and stay displayed with the field name, not the chosen value.

I guess some init signals are missing here. (And we suspect that init python scripts are not also loaded in this use case, but it's another bug request )

Please see the gif that show the behavior here https://share.oslandia.net/public/7df0b9 (better to download and display in a browser locally, direct display doesn't seem to work)


@qgib
Copy link
Contributor Author

qgib commented Mar 30, 2017

Author Name: Regis Haubourg (@haubourg)


  • 10865 removed quote_list.png

@qgib
Copy link
Contributor Author

qgib commented Apr 25, 2017

Author Name: Regis Haubourg (@haubourg)


Well, I hadn't seen correctly the problem:

If chain filters is displayed, the real value is not displayed at all in the widget when switching from on feature to another in attribute table view. This is nastier than I thought.

See attached images showing before and after the switch.


  • priority_id was changed from Normal to High
  • 10892 was configured as Sélection_016.png
  • 10893 was configured as Sélection_015.png

@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 Jul 25, 2017

Author Name: Giovanni Manghi (@gioman)


  • description was changed from When opening a standalone form, if chained filters were chosen, they are remembered and displayed correctly.
    In attribute form view, when switching from one form to another, the filters are not refreshed and stay displayed with the field name, not the chosen value.

I guess some init signals are missing here. (And we suspect that init python scripts are not also loaded in this use case, but it's another bug request )

Please see the gif that show the behavior here https://share.oslandia.net/public/7df0b9 (better to download and display in a browser locally, direct display doesn't seem to work) to When opening a standalone form, if chained filters were chosen, they are remembered and displayed correctly.
In attribute form view, when switching from one form to another, the filters are not refreshed and stay displayed with the field name, not the chosen value.

I guess some init signals are missing here. (And we suspect that init python scripts are not also loaded in this use case, but it's another bug request )

Please see the gif that show the behavior here https://share.oslandia.net/public/7df0b9 (better to download and display in a browser locally, direct display doesn't seem to work)

  • crashes_corrupts_data was changed from 0 to 1

@qgib
Copy link
Contributor Author

qgib commented Aug 18, 2017

Author Name: Paul Blottiere (Paul Blottiere)


Applied in changeset cea7bd3.


  • done_ratio was changed from 0 to 100
  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Aug 18, 2017
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Forms Crash/Data Corruption labels May 25, 2019
@qgib qgib added this to the Version 3.0 milestone 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! Crash/Data Corruption Forms High Priority
Projects
None yet
Development

No branches or pull requests

1 participant