When you are editing a Scene connection under the Data Source Manager and change the Name a new connection is created instead of changing the name of the selected connection.
If you create a new connection and enter the name of an existing Scene this scene is overwritten instead of creating a new connection.
Both of these behaviors might lead to confusion.
Steps to reproduce the issue
Open the Data Source Manager
Click on Scene in the left side menu.
(If a scene already exists skip to point 5)
Under Connections, click New, New Cesium 3D Tiles Connection...
Create a new scene, e.g. Name: Test, URL: http://example.com/. Click OK to store the connection.
Select the new connection in the drop-down under Connection. Press Edit.
Change the title from Test to e.g. Test2. Click OK to store the connection.
Notice the drop-down. There are now both a Test and a Test2 connection instead of just having the Test connection renamed.
Versions
QGIS version | 3.36.3-Maidenhead | QGIS code revision | 2df96554
-- | -- | -- | --
Qt version | 5.15.13
Python version | 3.12.3
GDAL/OGR version | 3.9.0
PROJ version | 9.4.0
EPSG Registry database version | v11.004 (2024-02-24)
GEOS version | 3.12.1-CAPI-1.18.1
SQLite version | 3.45.1
PDAL version | 2.6.3
PostgreSQL client version | 16.2
SpatiaLite version | 5.1.0
QWT version | 6.2.0
QScintilla2 version | 2.14.1
OS version | Windows 10 Version 2009
| | |
Active Python plugins
Dataforsyningen | 0.4
geosearch_dk | 2.0.4
GTFS-GO-master | 4.0.0
LAStools | 2.1.0
latlontools | 3.6.20
OSMDownloader | 1.0.3
plugin_reloader | 0.9.4
QuickOSM | 2.2.3
skraafoto | 0.2
sparqlunicorn | 0.15
db_manager | 0.1.20
grassprovider | 2.12.99
MetaSearch | 0.3.6
processing | 2.12.99
QGIS version
3.36.3-Maidenhead
QGIS code revision
[2df96554](https://github.com/qgis/QGIS/commit/2df96554)
Qt version
5.15.13
Python version
3.12.3
GDAL/OGR version
3.9.0
PROJ version
9.4.0
EPSG Registry database version
v11.004 (2024-02-24)
GEOS version
3.12.1-CAPI-1.18.1
SQLite version
3.45.1
PDAL version
2.6.3
PostgreSQL client version
16.2
SpatiaLite version
5.1.0
QWT version
6.2.0
QScintilla2 version
2.14.1
OS version
Windows 10 Version 2009
Active Python plugins
Dataforsyningen
0.4
geosearch_dk
2.0.4
GTFS-GO-master
4.0.0
LAStools
2.1.0
latlontools
3.6.20
OSMDownloader
1.0.3
plugin_reloader
0.9.4
QuickOSM
2.2.3
skraafoto
0.2
sparqlunicorn
0.15
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
### Supported QGIS version
- [X] I'm running a supported QGIS version according to [the roadmap](https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule).
### New profile
- [ ] I tried with a new [QGIS profile](https://docs.qgis.org/latest/en/docs/user_manual/introduction/qgis_configuration.html#working-with-user-profiles)
### Additional context
It seems like New and Edit works identically: If the name is unused a new connection is created. If the name is already used this connection is overwritten. This is not desirable.
What is the bug or the crash?
When you are editing a Scene connection under the Data Source Manager and change the Name a new connection is created instead of changing the name of the selected connection.
If you create a new connection and enter the name of an existing Scene this scene is overwritten instead of creating a new connection.
Both of these behaviors might lead to confusion.
Steps to reproduce the issue
Test
, URL:http://example.com/
. Click OK to store the connection.Test
to e.g.Test2
. Click OK to store the connection.Test
and aTest2
connection instead of just having theTest
connection renamed.Versions
QGIS version | 3.36.3-Maidenhead | QGIS code revision | 2df96554 -- | -- | -- | -- Qt version | 5.15.13 Python version | 3.12.3 GDAL/OGR version | 3.9.0 PROJ version | 9.4.0 EPSG Registry database version | v11.004 (2024-02-24) GEOS version | 3.12.1-CAPI-1.18.1 SQLite version | 3.45.1 PDAL version | 2.6.3 PostgreSQL client version | 16.2 SpatiaLite version | 5.1.0 QWT version | 6.2.0 QScintilla2 version | 2.14.1 OS version | Windows 10 Version 2009 | | | Active Python plugins Dataforsyningen | 0.4 geosearch_dk | 2.0.4 GTFS-GO-master | 4.0.0 LAStools | 2.1.0 latlontools | 3.6.20 OSMDownloader | 1.0.3 plugin_reloader | 0.9.4 QuickOSM | 2.2.3 skraafoto | 0.2 sparqlunicorn | 0.15 db_manager | 0.1.20 grassprovider | 2.12.99 MetaSearch | 0.3.6 processing | 2.12.99 QGIS version 3.36.3-Maidenhead QGIS code revision [2df96554](https://github.com/qgis/QGIS/commit/2df96554) Qt version 5.15.13 Python version 3.12.3 GDAL/OGR version 3.9.0 PROJ version 9.4.0 EPSG Registry database version v11.004 (2024-02-24) GEOS version 3.12.1-CAPI-1.18.1 SQLite version 3.45.1 PDAL version 2.6.3 PostgreSQL client version 16.2 SpatiaLite version 5.1.0 QWT version 6.2.0 QScintilla2 version 2.14.1 OS version Windows 10 Version 2009 Active Python plugins Dataforsyningen 0.4 geosearch_dk 2.0.4 GTFS-GO-master 4.0.0 LAStools 2.1.0 latlontools 3.6.20 OSMDownloader 1.0.3 plugin_reloader 0.9.4 QuickOSM 2.2.3 skraafoto 0.2 sparqlunicorn 0.15 db_manager 0.1.20 grassprovider 2.12.99 MetaSearch 0.3.6 processing 2.12.99 ### Supported QGIS version - [X] I'm running a supported QGIS version according to [the roadmap](https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule). ### New profile - [ ] I tried with a new [QGIS profile](https://docs.qgis.org/latest/en/docs/user_manual/introduction/qgis_configuration.html#working-with-user-profiles) ### Additional context It seems like New and Edit works identically: If the name is unused a new connection is created. If the name is already used this connection is overwritten. This is not desirable.