[GRASS-dev] Re: [GRASS GIS] #1441: Hard Copy Map Utility (wxPython wrapper for ps.map) text overlay is broken

[GRASS GIS]

#1441: Hard Copy Map Utility (wxPython wrapper for ps.map) text overlay is broken
-------------------------------------------+--------------------------------
 Reporter:  cmbarton                       |       Owner:  grass-dev@…              
     Type:  defect                         |      Status:  new                      
 Priority:  normal                         |   Milestone:  6.4.2                    
Component:  wxGUI                          |     Version:  svn-trunk                
 Keywords:  hard copy map utility, ps.map  |    Platform:  Unspecified              
      Cpu:  Unspecified                    |  
-------------------------------------------+--------------------------------

Comment(by cmbarton):

 I've been trying to work out the issues with management of color for text
 objects (including the 'map info' text object). The behavior is as
 follows:

 1) If border or background color is enabled but a color is not explicitly
 set, it raises the error of 'ps.map exited with a 1' (NB: this is a really
 useless error).

 2) If a background color or border color is set for a text object it seems
 to show up in the preview and final output pdf.

 3) If a background color or border color is set of a map info object, it
 may or may not show up in preview and output. I've yet to come up with a
 sequence of steps that make this happen or not.

 There are 2 sets of dictionaries of settings maintained by the ps modules.
 1 set is a dictionary for each class of function (text, legend, map info,
 etc); the other is a single large dictionaries of "instructions" that are
 used to build a ps.map script. AFAICT, the problems in # 1-3 above are
 probably a result of incomplete or incorrect updating between these two
 dictionary sets, and possibly between the dictionaries of settings and the
 actual interface controls.

 Nothing is standing out to me that is incorrect so far. So I'm recording
 this in case another set of eyes wants to take a look sometime. I'm not
 sure whether it is worth it yet to backport the changes to the GRASS 6
 branches I've done until these other issues are solved or not. It is
 working better than it was, but there are still these inconsistencies.

 Michael

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1441#comment:12>
GRASS GIS <http://grass.osgeo.org>