You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The GUI disregards an existing non-default database directory when automatically creating and activating a demo location.
To Reproduce
install GRASS from the master branch one or two months ago (it could be related to commit 28876fe)
configure a non-default GISDBASE in ~/.grass7/rc and fill it with a few locations and layers
exit GRASS, update to the current master branch and start it again
upon start the GUI will create a new database in ~/grassdata with a location named world_latlong_wgs84 and a vector layer, it will also switch to the new mapset
Expected behavior
It would seem more logical to create the demo location in the current database, and to prompt the user before doing so. Perhaps that's how it works when GISDBASE points to the default directory, but when it is different, the behaviour becomes inconsistent.
The text was updated successfully, but these errors were encountered:
Please, see #1400. Here is explained how the suggested startup is gonna look like.
As @HuidaeCho suggested, I will probably make another variable in rc called "default_gisdbase" which could be manually set up by a user.
Describe the bug
The GUI disregards an existing non-default database directory when automatically creating and activating a demo location.
To Reproduce
GISDBASE
in~/.grass7/rc
and fill it with a few locations and layers~/grassdata
with a location namedworld_latlong_wgs84
and a vector layer, it will also switch to the new mapsetExpected behavior
It would seem more logical to create the demo location in the current database, and to prompt the user before doing so. Perhaps that's how it works when
GISDBASE
points to the default directory, but when it is different, the behaviour becomes inconsistent.The text was updated successfully, but these errors were encountered: