[mapguide-internals] Advanced stylization - expression suppression required for numeric entities?

[Walt Welton-Lair]

For color, numeric, and boolean properties you don't need quotes.  The code first tries to evaluate the property as a constant, and only if that fails does it invoke the FDO expression engine.

For properties which are evaluated as strings, use single quotes to avoid invoking the expression engine.  Examples:

- specifying a constant label text:
<Text>'Park'</Text>

- specifying a constant enumerated value:
<HorizontalAlignment>'Center'</HorizontalAlignment>

In both examples leaving out the quotes will give the same result, but it will be slower.

Walt

________________________________________
From: mapguide-internals-bounces at lists.osgeo.org [mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch [jason at jasonbirch.com]
Sent: Thursday, December 31, 2009 3:37 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Advanced stylization - expression suppression     required for numeric entities?

Hi,

Previously, I believe that Walt indicated that you didn't have to quote
colour strings to avoid having them dealt with as FDO expressions, that they
would be evaluated as a colour based on a pattern.  Is there similar logic
in place for typically integer entities such as LineWeight, Height,
PositionX, PositionY, etc, or is it better to wrap numeric values in single
quotes to prevent evaluation?

Thanks,
Jason
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals