-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
CRS selector not working #31753
Comments
This affects also QGIS's "define layer projection". |
I can reproduce the problem with the CRS selector in QGIS 3.4.9 on Windows 10. The CRS selector of the plugin Offline-MapMatching (opened from the vector menu, toolbar and the toolbox) is also completely gray. I cannot reproduce the problem in QGIS 3.4 on macOS. |
Yeah, I have also seen this in plugins. |
I can confirm on QGIS 3.4.12 too. self.addParameter(
QgsProcessingParameterCrs(
self.CRS,
self.tr('Coordinate Reference System'),
)
) and makes it impossible to use the Processing algorithm. It's working well with a default CRS value such as: self.addParameter(
QgsProcessingParameterCrs(
self.CRS,
self.tr('Coordinate Reference System'),
defaultValue='EPSG:2154',
)
) |
@Gustry |
@gioman I don't know, I'm just working on a new Processing provider and I notice I needed to define a default projection to make it work. |
@Gustry thanks! anyone has idea about what is going on here? |
The fix might be: 63370d9 |
I have seen this on a number of 3.4.12 installations at a training, in this case in the CRS dialog of the "add delimited text layer" core tool. |
For me, the CRS selector doesn't work only in the "Add delimited text layer".
|
…p box Cherry-picked from 63370d9, fixes qgis#31753
Does this fix the issue with not being able to set the CRS in QGIS 3.4? |
This is in the GDAL tool "Export to PostgreSQL" (the dialog to choose a CRS is all greyed out).
As the parameters is mandatory (I believe it should not be) then the user cannot use the tool at all unless the needed CRS is among the list/dropdown of the latest used.
This affects 3.4 but not master (and I can't spot any important difference in the code in the the two versions, but of course I'm probably wrong).
The text was updated successfully, but these errors were encountered: