Feasibility-wise, it's very simple. All current overloads of RenderMap funnel into an internal RenderMapInternal method that does the actual rendering, but none of the overloads of RenderMap pass a selection color into the MgRenderingOptions used by RenderMapInternal, so it defaults to blue.
As mentioned, the solution is to simply offer one or more overloads of RenderMap that takes a selection color and have that particular overload pass the color down to RenderMapInternal. The question then is how many new overloads of RenderMap do you provide? Because there's many different signatures of RenderMap in the API. Do we replicate each overload that currently exists and provide a version that takes a selection color? Or just replicate the one that has the most parameters and provide copy of that overload that also takes a selection color. - Jackie -- View this message in context: http://osgeo-org.1560.x6.nabble.com/RenderMap-and-selection-color-wish-tp5100527p5100831.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
