[mapguide-internals] Re: Advanced stylization - global parameters
for compound symbols?
Jason Birch
jason at jasonbirch.com
Wed Dec 16 23:28:47 EST 2009
I didn't even think to try that; figured the name had to be unique for
some reason. I'm only really using name as metadata anyway, and xml
comments work just as well for that.
If that works, then I think its fine (for my use, for now) though I
think the global parameter is still a decent idea, and the blank value
works for me... I'll put in an enhancement request for this when I get
to a pc if this is reasonable.
Jason
On 2009-12-16, Walt Welton-Lair <walt.welton-lair at autodesk.com> wrote:
> Another way to make it work is to use the same name for each child symbol in
> the compound. Then the override gets applied to all child symbols with that
> name and that parameter ID.
>
> Keep in mind that if every child symbol in a compound has different
> parameter names then that increases the number of things the UI needs to be
> able to let the user control, whether at a global level or individual level.
> So for example if you want to individually control the color of two
> separate child symbols then use different parameter names for each one. But
> if you want the colors of both to always be the same then use the same
> parameter name.
>
> Making the symbol name optional in the override seems like a reasonable
> idea. To avoid a schema change (the SymbolName element is currently
> required) we could simply say that if the name is blank than it gets applied
> to all parameters with that identifier name.
>
> Walt
>
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
> Sent: Wednesday, December 16, 2009 4:12 PM
> To: MapGuide Internals Mail List
> Subject: [mapguide-internals] Advanced stylization - global parameters for
> compound symbols?
>
> Has any thought been given to a mechanism for setting a parameter override
> for a compound symbol at the global level and having it cascade down to all
> of the simple symbols within?
>
> I can think of a couple ways of doing this:
>
> - Make specification of the symbol name optional in the layer's override
> declaration, and have it apply to all parameters sharing that identifier
> within child simple symbols
> - Add some explicit mapping functionality to the compound symbol
> declaration
>
> Is there a mechanism for this that I'm missing? Is this a bad idea? I've
> run across a few cases already where I want to set the same colour and
> weight across a few different parts of a compound symbol, and getting
> annoyed having to set them all in the layer definition. If we ever do get a
> GUI for this it will be a bit of a mess in these cases...
>
> Jason
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
More information about the mapguide-internals
mailing list