#1068: unnecessary error information at GRASS startup
----------------------+-----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: wxGUI | Version: svn-releasebranch64
Keywords: | Platform: All
Cpu: All |
----------------------+-----------------------------------------------------
Don't issue an error when a location or mapset is no longer available at
startup, like:
{{{
Starting GRASS ...
BŁĄD:MAPSET ula nie został znaleziony
ERROR: Location <newLocation> not found
ERROR: Mapset <ula> not found
}}}
#1068: unnecessary error information at GRASS startup
-----------------------+----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: minor | Milestone: 6.4.0
Component: wxGUI | Version: svn-releasebranch64
Resolution: | Keywords:
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Changes (by martinl):
* priority: normal => minor
Comment:
Replying to [ticket:1068 msieczka]:
> Don't issue an error when a location or mapset is no longer available at
startup, like:
Why? It's kind of error...
{{{
> Starting GRASS ...
> BŁĄD:MAPSET ula nie został znaleziony
> ERROR: Location <newLocation> not found
> ERROR: Mapset <ula> not found
}}}
>
> This is scarry.
Really?
Well, this "message" doesn't seems to me to be a "defect"...
#1068: unnecessary error information at GRASS startup
-----------------------+----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: minor | Milestone: 6.4.0
Component: default | Version: svn-releasebranch64
Resolution: | Keywords:
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Changes (by msieczka):
* component: wxGUI => default
Comment:
> Why? It's kind of error...
I don't think so.
1. Remove or rename a location using the button at wxGUI startup.
2. Quit.
3. Start GRASS back - and it goes:
{{{
Starting GRASS ...
BŁĄD:MAPSET ula nie został znaleziony
ERROR: Location <newLocation> not found
ERROR: Mapset <ula> not found
}}}
or e.g.:
{{{
access: No such file or directory
ERROR: LOCATION << /home/grassdata/newLocation2 >> not available
}}}
It is not an error for the location or mapset to be no longer available
under the last path GRASS remembered. IMO startup procedure should handle
this normally. If it can't - OK, too bad. Though I still would say this is
weird.
>> This is scarry.
> Really?
No, actually it's "scary" :).
Seriously, I really mean the user might be at least surprised with GRASS
telling him it is an error that the location/mapset does not longer exist,
while he removed/changed it's name using a regular GRASS tool.
#1068: unnecessary error information at GRASS startup
----------------------+-----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@…
Type: defect | Status: new
Priority: minor | Milestone: 6.4.0
Component: Startup | Version: svn-releasebranch64
Keywords: | Platform: All
Cpu: All |
----------------------+-----------------------------------------------------
Changes (by hamish):
* component: Default => Startup
Comment:
If the last-known mapset or location isn't found any more, an error saying
it isn't found seems entirely appropriate. The expected behaviour (load up
the last mapset) is not possible, and any time that the expected thing
isn't going to happen there should be warning bells sounding.
The thing to worry about, I think, is how well it recovers from that
situation..
the current 6.x wxGUI gives this in the terminal if the mapset went away:
{{{
...
ERROR: MAPSET user1 not found
ERROR: Mapset <user1> not found
}}}
but loads up the loc'n with the list of existing mapsets.
If the loc'n is no longer there the wxGUI startup gives you:
{{{
Cleaning up temporary files ...
Starting GRASS ...
access: No such file or directory
ERROR: LOCATION << /path/to/old/name >> not available
}}}
then loads up the GISDBASE dir and selects the first loc'n there.
The -text version gives this after esc-enter, then asks if you want to
create it.
{{{
Mapset <<user1>> is not available
}}}
For an invalid loc'n it is similar: asks if you wish to create a new loc'n
by that name.
#1068: unnecessary error information at GRASS startup
-----------------------+----------------------------------------------------
Reporter: msieczka | Owner: grass-dev@…
Type: defect | Status: closed
Priority: minor | Milestone: 6.4.0
Component: Startup | Version: svn-releasebranch64
Resolution: wontfix | Keywords:
Platform: All | Cpu: All
-----------------------+----------------------------------------------------
Comment(by wenzeslaus):
Leaving as ''wontfix'' but note that there are some people that really
think that a user should not be scarred by application's messages:
Messages should be:
* ...
* Informative and constructive. Tell the user the reason for a problem
and help on how to solve the problem.
* Polite, non-terrifying and non-blaming. Avoid wording that terrifies
the user ("fatal", "illegal"), blames him for his behavior, and be polite.
