#757: WinGRASS: GUI window from cmd line
-------------------------+--------------------------------------------------
Reporter: silviap | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: default | Version: unspecified
Keywords: | Platform: Unspecified
Cpu: Unspecified |
-------------------------+--------------------------------------------------
When starting GRASS with the MinGW shell it just gives the help in the
shell, rather than opening the module's dialog.
Replying to [comment:3 hamish]:
> > which icon did you start with? The blue "M" or the blue "M"
> > with the GRASS logo in it or another?
Replying to [comment:4 silviap]:
> The blue M (MinGW shell)
I don't have it running in front of me so I may be mistaken, but I think
the one you want is the M with the grass white diamond logo half over the
top of it, or the white diamond one by itself. I think the blue M alone is
just the MSys UNIX shell ... not actually GRASS at all.
try this one:
source:grass/trunk/mswindows/Installer-Files/GRASS_MSys.ico
or try this one:
source:grass/trunk/mswindows/Installer-Files/GRASS.ico
but not this:
source:grass/trunk/mswindows/Installer-Files/MSYS_Custom_Icon.ico
Replying to [comment:5 hamish]:
> Replying to [comment:3 hamish]:
> > > which icon did you start with? The blue "M" or the blue "M"
> > > with the GRASS logo in it or another?
>
> Replying to [comment:4 silviap]:
> > The blue M (MinGW shell)
>
>
> I don't have it running in front of me so I may be mistaken, but I think
the one you want is the M with the grass white diamond logo half over the
top of it, or the white diamond one by itself. I think the blue M alone is
just the MSys UNIX shell ... not actually GRASS at all.
I don't have it running in front of me as well... so it was the M with the
grass logo, not just the MSys icon - the grass shell and not just the MSys
Unix shell. Colin agrees that it just gives the help in the shell, rather
than opening the module's dialog. So I just opened a ticket.
> try this one:
> source:grass/trunk/mswindows/Installer-Files/GRASS_MSys.ico
>
> or try this one:
> source:grass/trunk/mswindows/Installer-Files/GRASS.ico
>
> but not this:
> source:grass/trunk/mswindows/Installer-Files/MSYS_Custom_Icon.ico
>
>
> Hamish
A bit of misunderstanding here. GRASS is starting fine, but once open the
dialogs of individual modules aren't opening when they are typed into the
shell. Instead if you type {{{ r.walk }}} or whatever, the module's ascii
help text is output to the shell (as required arguments are missing, ie.
output) instead of opening a dialog window where the arguments may be
entered.
Replying to [comment:7 cnielsen]:
> A bit of misunderstanding here. GRASS is starting fine, but once open
the dialogs of individual modules aren't opening when they are typed into
the shell. Instead if you type {{{ r.walk }}} or whatever, the module's
ascii help text is output to the shell (as required arguments are missing,
ie. output) instead of opening a dialog window where the arguments may be
entered.
>
> -Colin
GRASS is starting fine, thank you for explaining it better and sorry for
creating the misunderstanding.
> A bit of misunderstanding here. GRASS is starting fine, but once open
the dialogs of individual modules aren't opening when they are typed into
the shell. Instead if you type {{{ r.walk }}} or whatever, the module's
ascii help text is output to the shell (as required arguments are missing,
ie. output) instead of opening a dialog window where the arguments may be
entered.
When you run the command without arguments, the GUI interface is only
generated if stdin is a terminal, according to isatty().
On Windows, isatty() only recognises the standard Windows Command Prompt
as a terminal. The MSys terminal (rxvt) isn't considered a terminal by
isatty() (AFAICT, any child processes will have their standard descriptors
connected to pipes).
I'm not sure that there is anything which can be done about this, other
than skipping the isatty() check altogether on Windows (although that may
be an acceptable solution; I don't know of a reason why the check is
actually necessary).
#757: WinGRASS: GUI window from cmd line
-------------------------+--------------------------------------------------
Reporter: silviap | Owner: grass-dev@…
Type: task | Status: new
Priority: trivial | Milestone: 6.4.0
Component: wxGUI | Version: 6.4.0 RCs
Keywords: wingrass | Platform: MSWindows XP
Cpu: Unspecified |
-------------------------+--------------------------------------------------
Comment(by hellik):
Replying to [comment:8 silviap]:
> Replying to [comment:7 cnielsen]:
> > A bit of misunderstanding here. GRASS is starting fine, but once open
the dialogs of individual modules aren't opening when they are typed into
the shell. Instead if you type {{{ r.walk }}} or whatever, the module's
ascii help text is output to the shell (as required arguments are missing,
ie. output) instead of opening a dialog window where the arguments may be
entered.
> >
> > -Colin
>
> GRASS is starting fine, thank you for explaining it better and sorry for
creating the misunderstanding.
Glynn wrote:
> When you run the command without arguments, the GUI
> interface is only generated if stdin is a terminal,
> according to isatty().
>
> On Windows, isatty() only recognises the standard
> Windows Command Prompt as a terminal. The MSys
> terminal (rxvt) isn't considered a terminal by isatty()
...
> You can still force a GUI using the --ui switch.
the problem is well understood; I just tested and the --ui work-around
still works; closing the ticket with the nearest reason to "cantfix".
