#1103: WinGrass64 - windows-commandline not released
-------------------------+--------------------------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 6.4.1
Component: Packaging | Version: svn-releasebranch64
Keywords: wingrass, | Platform: MSWindows Vista
Cpu: All |
-------------------------+--------------------------------------------------
thinking about ticket #1092 (http://trac.osgeo.org/grass/ticket/1092) and
an improved
WinGrass - R integration in the Windows-world, there is following issue
with WinGrass64:
by clicking on the desktop-shortcut "GRASS 6.4.SVN" (nightly build), there
is a windwows-command-
line started in the background of the wx-gui.
but the windows-command-line isn't released, so there's no access to the
command-line.
in WinGrass7 (nightly build) the windows-commandline is released and with
ticket #1092 you can start R within a WinGrass7-session
in the windows-command-line.
so any hints for improving this situation for WinGrass64?
#1103: WinGrass64 - windows-commandline not released
-------------------------+--------------------------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 6.4.2
Component: Packaging | Version: svn-releasebranch64
Keywords: wingrass, | Platform: MSWindows Vista
Cpu: All |
-------------------------+--------------------------------------------------
Comment(by hellik):
Replying to [ticket:1103 hellik]:
>
> so any hints for improving this situation for WinGrass64?
maybe any ideas for following situation?
- starting "WinGRASS6.4.1 Command Line"
- do ''g.gui wxpython''
- the wxgui is starting, but it's not possible to type anything in the
windows command line because it's locked as long the wxgui is opened
any hints what to do that the windows command line isn't locked as long
the wxgui is opened?
#1103: WinGrass64 - windows-commandline not released
-------------------------+--------------------------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 6.4.2
Component: Packaging | Version: svn-releasebranch64
Keywords: wingrass, | Platform: MSWindows Vista
Cpu: All |
-------------------------+--------------------------------------------------
Changes (by smitch):
* cc: smitch (added)
Comment:
Just found this bug report while searching for hints on the same problem
in our GIS lab. In our case, GRASS was installed using OSGEO4W, but the
symptoms are the same. If the wxpython GUI is selected as the current
interface, the command prompt is not interactive.
Workaround we're using for now: students are told to launch the OSGEO4W
shell, then from within that use grass64 -gui to fire up the old TclTk GUI
so they can choose their mapset etc., then quit the gui, then in the
shell, enter
g.gui gui=wxpython&
so that wxpython goes into the background as it should.
I have not had time to look at the grass64 batch file to compare how
wxpython is fired up compared to the tcltk version, but clearly the old
way is "correct" at least in terms of user experience.
#1103: WinGrass64 - windows-commandline not released
-------------------------+--------------------------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 6.4.4
Component: Packaging | Version: svn-releasebranch64
Keywords: wingrass, | Platform: MSWindows Vista
Cpu: All |
-------------------------+--------------------------------------------------
Comment(by hamish):
idea: have the startup .bat file (grass643svn.bat) as its last command
call "g.gui -wx", which should launch the GUI and safely background it in
C with G_spawn_ex(). I'm not sure if the .bat would then exit or go to the
GRASS> prompt, if exit maybe have it run bash.exe or cmd.exe to keep the
session alive?