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

QgsProcessingParameterNumber widget showing values outside the specified minValue to maxValue range #47244

Closed
1 of 2 tasks
janzandr opened this issue Feb 8, 2022 · 2 comments · Fixed by #47296
Closed
1 of 2 tasks
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@janzandr
Copy link

janzandr commented Feb 8, 2022

What is the bug or the crash?

When using an input number between 0 and 1, the user can enter values outside the valid range, e.g. -0.5

image

image

Steps to reproduce the issue

  1. In the model designer, just specify the input number as shown above.
  2. Run the model.
  3. Enter -0.5

Versions

QGIS version
3.22.1-Białowieża
QGIS code revision
663dcf8
Qt version
5.15.2
Python version
3.9.5
GDAL/OGR version
3.4.0
PROJ version
8.2.0
EPSG Registry database version
v10.038 (2021-10-21)
GEOS version
3.10.0-CAPI-1.16.0
SQLite version
3.35.2
PDAL version
2.3.0
PostgreSQL client version
13.0
SpatiaLite version
5.0.1
QWT version
6.1.3
QScintilla2 version
2.11.5
OS version
Windows 10 Version 2009

Active Python plugins
BitFlagRenderer
0.4.20200817T093838.master
changeDataSource
3.1
DataPlotly
3.8.1
ee_plugin
0.0.4
enmapboxplugin
3.10.20220125T085726.develop
force4qgis
1.0.1
InvisibleLayersAndGroups
2.1
rasterdataplotting
1.6.3
rastertimeseriesmanager
1.8
timeseriesviewerplugin
1.17.20210312T143004.master
zoomview
1.1.1
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.5
processing
2.12.99

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

  • I tried with a new QGIS profile

Additional context

No response

@janzandr janzandr added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Feb 8, 2022
@nicogodet
Copy link
Member

OK if parameter is mandatory but NOK if it's optionnal.

If you set a max bigger than 1 (ex: 2) and use CTRL+wheel to change the value (using decimals) the range goes from -1 to 2.

@ismailsunni
Copy link
Contributor

ismailsunni commented Feb 11, 2022

It seems only happens when the minimum is 0, and the type is float also. And if you put less than -1, it will be rejected

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.

3 participants