-
-
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
Impossible to change value when a range double spinbox is used and allow null value #26351
Comments
Author Name: Nyall Dawson (@nyalldawson) Already fixed in master/3.0.1
|
Author Name: Harrissou Santanna (@DelazJ) That's weird because i used the latest osgeo4w nightly build (unless the fix is really recent) |
Author Name: Harrissou Santanna (@DelazJ) Still present and really annoying (particularly for users that don't check the attribute forms tab)
|
Author Name: Giovanni Manghi (@gioman) Please try on QGIS 3.4.1, if the issue is still valid change the affected version, thanks.
|
Author Name: Jürgen Fischer (@jef-n) 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.
|
Author Name: Harrissou Santanna (@DelazJ)
Original Redmine Issue: 18463
Affected QGIS version: 3.3(master)
Redmine category:forms
Create a point temporary layer and in its layer properties dialog add a new integer field
OK
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.
The text was updated successfully, but these errors were encountered: