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

Form view gets stuck in the last shown not-NULL-value for some attributes when browsing through data #38552

Closed
RobinRots opened this issue Sep 2, 2020 · 1 comment · Fixed by #38801
Assignees
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@RobinRots
Copy link

RobinRots commented Sep 2, 2020

Describe the bug
I noticed not all values are refreshing (the value of a previous clicked feature is shown) as expected when browsing my data in the form view of the attribute table. On a closer look it appear to be columns for which the value is NULL which get stuck in the last shown not-NULL-value.

How to Reproduce

I attached a trimmed down version of the project and geopackage which shows the behaviour.

  1. Open the attribute table of the layer "Inventarisatie"
  2. Switch to Form view if necessary
  3. Randomly click different features in the left pane
  4. See error: the values for EENH3, EENH4, EENH5, EENH6 seem to get stuck (they are not refreshed with each click). Strangely enough, it's not always the same amount of fields that seem to be stuck. After a closer look I found out it's the columns for which the value is NULL which stay stuck in the last shown not-NULL-value.

QGIS and OS versions

QGIS version 3.14.15-Pi QGIS code revision d5114d2
Compiled against Qt 5.11.2 Running against Qt 5.11.2
Compiled against GDAL/OGR 3.0.4 Running against GDAL/OGR 3.0.4
Compiled against GEOS 3.8.1-CAPI-1.13.3 Running against GEOS 3.8.1-CAPI-1.13.3
Compiled against SQLite 3.29.0 Running against SQLite 3.29.0
PostgreSQL Client Version 11.5 SpatiaLite Version 4.3.0
QWT Version 6.1.3 QScintilla2 Version 2.10.8
Compiled against PROJ 6.3.2 Running against PROJ Rel. 6.3.2, May 1st, 2020
OS Version Windows 10 (10.0)
Active python plugins autoSaver; batchvectorlayersaver; BulkVectorExport; geopunt4Qgis; layerGroupFilter; OSMDownloader; qfieldsync; QuickOSM; quick_map_services; refFunctions; SelectWithin; splitmultipart; SpreadsheetLayers; db_manager; MetaSearch; processing

Additional context

Note, the fields I mention are all using the Value Relation widget, also the form is set up with several tabs. Maybe the problem has something to do with that...

bugreport_formview.zip

@RobinRots RobinRots added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Sep 2, 2020
@RobinRots RobinRots changed the title Form view doesn't refresh all values when browsing through data Form view gets stuck in the last shown not-NULL-value for some attributes when browsing through data Sep 3, 2020
@RobinRots
Copy link
Author

I just checked within an older version of QGIS (3.10.2) and it also shows the same error.

@elpaso elpaso self-assigned this Sep 16, 2020
elpaso added a commit to elpaso/QGIS that referenced this issue Sep 16, 2020
When there is no match in the relation layer,
show "(no selection)" instead of NOT updating
the widget (which was the reported issue).

Fixes qgis#38552
nyalldawson pushed a commit to nyalldawson/QGIS that referenced this issue Oct 5, 2020
When there is no match in the relation layer,
show "(no selection)" instead of NOT updating
the widget (which was the reported issue).

Fixes qgis#38552

(cherry picked from commit 448f7d9)
nyalldawson pushed a commit that referenced this issue Oct 23, 2020
When there is no match in the relation layer,
show "(no selection)" instead of NOT updating
the widget (which was the reported issue).

Fixes #38552

(cherry picked from commit 448f7d9)
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!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants