[GRASS-dev] [GRASS GIS] #1103: WinGrass64 - windows-commandline not released

[GRASS GIS]

#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.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/1103#comment:3>
GRASS GIS <http://grass.osgeo.org>