Bug report #18463

Impossible to change value when a range double spinbox is used and allow null value

Added by Harrissou Santanna over 4 years ago. Updated almost 4 years ago.

Affected QGIS version:3.3(master) Regression?:No
Operating System: Easy fix?:No
Pull Request or Patch supplied:No Resolution:no timely feedback
Crashes QGIS or corrupts data:Yes Copied to github as #:26351


Create a point temporary layer and in its layer properties dialog add a new integer field
Reopen the dialog in Attribute Forms tab
The created field is set as a "Range" editable allowing null value.
In the map canvas add a feature and try to set a value in the field: here, the Up and down arrow do not change anything (NULL is diplayed in the field) and if I manually type in a numeric value, it's cleared and replaced by NULL as soona s I leave the field.
This happens in the form and the attribute table.

I just got it worked when I unchecked the "Allow NULL values" option.

Btw checking the "Allow NULL values" when there are already data set the values to NULL in the field.


#1 Updated by Nyall Dawson over 4 years ago

  • Status changed from Open to Closed
  • Resolution set to fixed/implemented

Already fixed in master/3.0.1

#2 Updated by Harrissou Santanna over 4 years ago

That's weird because i used the latest osgeo4w nightly build (unless the fix is really recent)

#3 Updated by Harrissou Santanna over 4 years ago

  • Resolution deleted (fixed/implemented)
  • Status changed from Closed to Reopened

Reopening because as mentioned the issue is still there (4fb9091e6e).

#4 Updated by Harrissou Santanna about 4 years ago

  • Affected QGIS version changed from 3.1(master) to 3.3(master)

Still present and really annoying (particularly for users that don't check the attribute forms tab)

#5 Updated by Giovanni Manghi about 4 years ago

  • Status changed from Reopened to Feedback

Please try on QGIS 3.4.1, if the issue is still valid change the affected version, thanks.

#6 Updated by Jürgen Fischer almost 4 years ago

  • Status changed from Feedback to Closed
  • Resolution set to no timely feedback

Bulk closing 82 tickets in feedback state for more than 90 days affecting an old version. Feel free to reopen if it still applies to a current version and you have more information that clarify the issue.

Also available in: Atom PDF