[GRASS-dev] Re: [GRASS GIS] #1239: wxGUI command layer broken and unusable

[GRASS GIS]

#1239: wxGUI command layer broken and unusable
-------------------------+--------------------------------------------------
 Reporter:  garu         |       Owner:  grass-dev@…              
     Type:  defect       |      Status:  new                      
 Priority:  major        |   Milestone:  6.4.1                    
Component:  wxGUI        |     Version:  6.4.0                    
 Keywords:               |    Platform:  MSWindows XP             
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by cmbarton):

 Replying to [comment:5 glynn]:
 > Replying to [comment:4 garu]:
 >
 > > 1) it looks that Grass commands counts in the order of hundreds, do
 really all of them have their graphical layer correspondence? I doubt, so
 i think the command layer is the only option if a user wants to introduce
 in the map stack some "esoteric" command.
 >
 > Most of them don't generate graphical output, so they can't be used from
 a command layer. However, there are existing scripts which can generate
 graphical output yet don't have a specific menu item in the GUI, and the
 user can always create their own scripts which generate display output.


 This is the best reason I've heard so far for trying to fix this. My point
 to Gabrielle was simply that this is broken and wondered if there is a
 reason to go to the effort to fix it since it duplicates other functions.
 However, if a user writes a script that creates graphic output, it could
 be nice to display the results along with other graphic layers and a
 command layer is a good place to do this.

 I agree that the most robust way for this to work is to have it mirror the
 other display layers and pop up one of the GUI dialogs for setting
 options. That way, it parses exactly like the other layers. To do this,
 either a new button would need to be added to the command layer line (and
 this could be more of a pain than it seems, give the way this control
 works) or parse a special key (return or tab probably) to pop up the
 settings dialog for the command.

 Michael

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