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

GRASS GIS trac at osgeo.org
Fri Sep 9 12:12:42 EDT 2011


#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):

 Replying to [comment:14 annakrat]:
 > Replying to [comment:12 cmbarton]:
 > > 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).
 >
 > I cannot reproduce this error, do you talk about map info or text?
 >
 > > 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.
 >
 > I fixed the background color of text in draft mode. I tried to draw the
 text border in draft mode but it kept disappearing. I couldn't find the
 problem so I left it without it. Maybe a tooltip or a static label could
 inform user that not all features are visible in draft mode (like text
 highlight).
 >
 > > 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.
 > The color in draft mode is always blue and it has no other meaning. In
 preview mapinfo background color depends on its position, see #192
 >
 >

 I'm close to fixing this, but have not yet committed those changes because
 they still have a few weird inconsistencies that have to do with updating
 after a drag event. I'll see how your changes mesh with mine. It's a
 pretty busy day today so I might not get to it until the weekend.

 Michael

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



More information about the grass-dev mailing list