[GRASS-dev] [GRASS GIS] #1891: wingrass: background dosbox from regular wxgui startup

GRASS GIS trac at osgeo.org
Mon Feb 17 03:32:09 PST 2014


#1891: wingrass: background dosbox from regular wxgui startup
----------------------+-----------------------------------------------------
 Reporter:  hamish    |       Owner:  grass-dev@…              
     Type:  defect    |      Status:  new                      
 Priority:  major     |   Milestone:  6.4.3                    
Component:  Default   |     Version:  svn-releasebranch64      
 Keywords:  wingrass  |    Platform:  MSWindows 7              
      Cpu:  x86-64    |  
----------------------+-----------------------------------------------------

Comment(by marisn):

 Replying to [comment:51 hamish]:
 > Replying to [comment:50 neteler]:
 > > The dosbox is minimized as desired.
 >
 > (1)current way in G7, some votes to do that in G6

 Current approach in G7 is broken by design.

 When the user starts GRASS for the first time, grass70.py is printing in
 the CMD window "Welcome to blahblah press RETURN to continue". As of
 current nightly, CMD window is minimised thus user doesn't see that
 message. From ~20 persons only one guessed correctly - hey, there could be
 something important in that minimized window!

 Potential solutions:
  * do not print a welcome message in CMD. Why it could not be a pop-up in
 WXGUI?
  * do not minimize CMD window by default.

 The GRASS configuration information is stored ONLY when user types into
 CMD "exit" to close the minimized window. Out of ~20 users NONE knew the
 necessity to maximize the CMD window and type in "exit" instead of just
 closing the CMD window.

 Potential solutions:
  * do not release CMD when starting gui. Thus on GUI exit it would be
 possible to close CMD too and write out configuration data, clean up TMP
 files etc. CMD could be provided by a separate icon - "GRASS GUI with
 CMD".
  * do not minimize CMD window if one expects to type "exit" to close it.
  * or better - trap window close event and run "exit" part of code to
 clean up on such event.

 Adding to this ticket, as decision making process has been made here.

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



More information about the grass-dev mailing list