after finishing g.gui.rlisetup there is a message the the user defined
config file is created, but there is no information about the path to the
config file.
in windows it is e.g.
{{{
C:\Users\xxx\AppData\Roaming\GRASS7\r.li
}}}
it would be nice if there would be an information of the whole path to the
file which could be copy/paste as input to the r.li.*-modules.
#2846: g.gui.rlisetup: show where new config file is created
--------------------------+---------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.4
Component: Raster | Version: svn-releasebranch70
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+---------------------------------
Comment (by mlennert):
Replying to [ticket:2846 hellik]:
> it would be nice if there would be an information of the whole path to
the file which could be copy/paste as input to the r.li.*-modules.
You should not use the absolute path in the r.li.* modules. Just the file
name. You can list existing files with g.gui.rlisetup. So, normally, no
need to see the absolute path.
However, ascii output files are also stored in the same path, and this is
a bit more of a nuisance as you then have to navigate there to find the
file. I imagine (but haven't checked) that this was done to ensure that
any other r.li.* module can potentially, easily find the ascii output of
another, but are there many modules that read this kind of output ?
In any case, though, all modules give the info of the standard path in
their manual. Ex for r.li.padsd:
"[...] otherwise an ASCII file will be generated in the folder
C:\Users\userxy\AppData\Roaming\GRASS7\r.li\output\ (MS-Windows) or
$HOME/.grass7/r.li/output/ (GNU/Linux)."
#2846: g.gui.rlisetup: show where new config file is created
--------------------------+---------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.4
Component: Raster | Version: svn-releasebranch70
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+---------------------------------
Comment (by lucadelu):
Replying to [comment:2 mlennert]:
> Replying to [ticket:2846 hellik]:
> > it would be nice if there would be an information of the whole path to
the file which could be copy/paste as input to the r.li.*-modules.
>
> You should not use the absolute path in the r.li.* modules. Just the
file name. You can list existing files with g.gui.rlisetup. So, normally,
no need to see the absolute path.
>
I confirm this
> However, ascii output files are also stored in the same path, and this
is a bit more of a nuisance as you then have to navigate there to find the
file. I imagine (but haven't checked) that this was done to ensure that
any other r.li.* module can potentially, easily find the ascii output of
another, but are there many modules that read this kind of output ?
>
Maybe you can open an enhancement ticket for this?
Can I suggest to close this ticket as invalid? I think it is better to use
g.gui.rlisetup to create or modify the r.li configuration files.
#2846: g.gui.rlisetup: show where new config file is created
--------------------------+---------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.4
Component: Raster | Version: svn-releasebranch70
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+---------------------------------
Comment (by hellik):
Replying to [comment:3 lucadelu]:
> Replying to [comment:2 mlennert]:
> > Replying to [ticket:2846 hellik]:
> > > it would be nice if there would be an information of the whole path
to the file which could be copy/paste as input to the r.li.*-modules.
> >
> > You should not use the absolute path in the r.li.* modules. Just the
file name. You can list existing files with g.gui.rlisetup. So, normally,
no need to see the absolute path.
> >
>
> I confirm this
>
> > However, ascii output files are also stored in the same path, and this
is a bit more of a nuisance as you then have to navigate there to find the
file. I imagine (but haven't checked) that this was done to ensure that
any other r.li.* module can potentially, easily find the ascii output of
another, but are there many modules that read this kind of output ?
> >
>
> Maybe you can open an enhancement ticket for this?
>
> Can I suggest to close this ticket as invalid? I think it is better to
use g.gui.rlisetup to create or modify the r.li configuration files.
What kind of invalid is to show the path to config (and maybe the output)
files?
#2846: g.gui.rlisetup: show where new config file is created
--------------------------+---------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.4
Component: Raster | Version: svn-releasebranch70
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+---------------------------------
Comment (by mlennert):
Replying to [comment:4 hellik]:
> Replying to [comment:3 lucadelu]:
> > Replying to [comment:2 mlennert]:
> > > Replying to [ticket:2846 hellik]:
> > > > it would be nice if there would be an information of the whole
path to the file which could be copy/paste as input to the r.li.*-modules.
> > >
> > > You should not use the absolute path in the r.li.* modules. Just the
file name. You can list existing files with g.gui.rlisetup. So, normally,
no need to see the absolute path.
> > >
> >
> > I confirm this
> >
> > > However, ascii output files are also stored in the same path, and
this is a bit more of a nuisance as you then have to navigate there to
find the file. I imagine (but haven't checked) that this was done to
ensure that any other r.li.* module can potentially, easily find the ascii
output of another, but are there many modules that read this kind of
output ?
> > >
> >
> > Maybe you can open an enhancement ticket for this?
> >
> > Can I suggest to close this ticket as invalid? I think it is better to
use g.gui.rlisetup to create or modify the r.li configuration files.
>
> What kind of invalid is to show the path to config (and maybe the
output) files?
I think that a message with the full path will give the illusion that this
is what users should use, while what they actually should use is just the
name. Maybe to make that even clearer, the r.li.* modules should provide a
dropdown list of available config files (such as the list of signature
files you can get in i.maxlik). Again, something for an enhancement
ticket.
So, maybe invalid is a bit harsh, and wontfix is better, but I agree with
Luca on the conclusion.
- created the config-file by g.gui.rlisetup
- closing g.gui.rlisetup-GUI
- starting the r.li.patchdensity-GUI
- then in the r.li.patchdensity-GUI regarding for config-file I have to
browse through the file system to the config file
but I from ''a user perspective'': you don't know where to browse to the
config file, as there is no information where the config file was created.
reopening the ticket, as there is actually a lack of information where to
browse.
#2846: g.gui.rlisetup: show where new config file is created
--------------------------+---------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: reopened
Priority: normal | Milestone: 7.4.0
Component: Raster | Version: svn-releasebranch70
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+---------------------------------
Comment (by hellik):
Replying to [comment:5 mlennert]:
> Replying to [comment:4 hellik]:
> > Replying to [comment:3 lucadelu]:
> > > Replying to [comment:2 mlennert]:
> > > > Replying to [ticket:2846 hellik]:
> > > > > it would be nice if there would be an information of the whole
path to the file which could be copy/paste as input to the r.li.*-modules.
> > > >
> > > > You should not use the absolute path in the r.li.* modules. Just
the file name. You can list existing files with g.gui.rlisetup. So,
normally, no need to see the absolute path.
> > > >
> > >
> > > I confirm this
> > >
> > > > However, ascii output files are also stored in the same path, and
this is a bit more of a nuisance as you then have to navigate there to
find the file. I imagine (but haven't checked) that this was done to
ensure that any other r.li.* module can potentially, easily find the ascii
output of another, but are there many modules that read this kind of
output ?
> > > >
> > >
> > > Maybe you can open an enhancement ticket for this?
> > >
> > > Can I suggest to close this ticket as invalid? I think it is better
to use g.gui.rlisetup to create or modify the r.li configuration files.
> >
> > What kind of invalid is to show the path to config (and maybe the
output) files?
>
> I think that a message with the full path will give the illusion that
this is what users should use, while what they actually should use is just
the name. Maybe to make that even clearer, the r.li.* modules should
provide a dropdown list of available config files (such as the list of
signature files you can get in i.maxlik). Again, something for an
enhancement ticket.
>
a dropdown list would be indeed the best solution.
> So, maybe invalid is a bit harsh, and wontfix is better, but I agree
with Luca on the conclusion.
as long there is no dropdown list, IMHO the user is left alone to know
names if there are several config files.
#2846: g.gui.rlisetup: show where new config file is created
--------------------------+---------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: reopened
Priority: normal | Milestone: 7.4.0
Component: Raster | Version: svn-releasebranch70
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+---------------------------------
Comment (by lucadelu):
Replying to [comment:10 hellik]:
> but I from ''a user perspective'': you don't know where to browse to the
config file, as there is no information where the config file was created.
>
> reopening the ticket, as there is actually a lack of information where
to browse.
>
the problem is not related to g.gui.rlisetup, so please close this ticket
and fill new one
#2846: g.gui.rlisetup: show where new config file is created
--------------------------+---------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: reopened
Priority: normal | Milestone: 7.4.0
Component: Raster | Version: svn-releasebranch70
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+---------------------------------
Comment (by hellik):
Replying to [comment:12 lucadelu]:
> Replying to [comment:10 hellik]:
>
>
> > but I from ''a user perspective'': you don't know where to browse to
the config file, as there is no information where the config file was
created.
> >
> > reopening the ticket, as there is actually a lack of information where
to browse.
> >
>
> the problem is not related to g.gui.rlisetup, so please close this
ticket and fill new one