4.8.2?

[Steve Lime]

Jani: Lemme get back to you on the leaks. 

I don't believe 1)  is a problem even after reverting because the scaling is always done based on the symbol before rotation. 

Steve

>>> Jani Averbach <javerbach at EXTENDTHEREACH.COM> 03/06/06 2:59 PM >>>
> -----Original Message-----
> From:  On Behalf Of Steve Lime
> Sent: Monday, March 06, 2006 9:02 AM
> Subject: Re: 4.8.2?
> 
> This is the status as far as I know. I'll gladly help however I can.
> 
> >   - rolling back the symbol size computation to use just height (4.6
=
> >     behavior)
>   1) Jani was handling

OK, I have few comments/questions:

1) What happens when someone rotates a symbol?
   Let's say that I have (x,y) 2x100 pixmap symbol, and I rotate
   it 90deg, and say that my symbol size is 100. What should happen,
   is the symbol now 100x5000, or is it still 100x2?  What if I rotated
it
   only 45deg?


2) Secondly, I think I have found few memory leaks:

   mapsymbol.c: *msRotateSymbol
	
   At the line 1180 we allocate a new symbolObj, and then on the line
1188     (case MS_SYMBOL_ELLIPSE) we just return symbol,
   without freeing the newSymbol.
  
   In case of VECTOR we return the newSymbol (1233)

   In case of PIXMAP we return the newSymbol (1281)

   In case of TRUETYPE or 'default' we return the symbol (1286 and
   1290).

   So inside this function, we leak memory in three cases, and
   later when we are using this new symbol, we are leaking more:
   
   mapgd.c: msDrawMarkerSymbolGD

   in case of PIXMAP (1644), we are storing msRotateSymbol return
   value to symbol, but we are not releasing that value. The same
   thing is happening with VECTOR (1711).

If I am wrong, please correct me.


BR, Jani

SRC,LLC 
SRC in Action:
http://www.DemographicsNow.com 

Join SRC at Extend 2006 - Disruptive Technology June 5-7, 2006 at the
Hyatt
Regency, Huntington Beach, CA For more details, click here:
http://www.extendthereach.com/extend06/