When you add a layer to the Map Definition, if it is the first layer to be added, Maestro tries to be smart and grabs the extents of that layer and sets the extents of the Map Definition to match.
This obviously naively assumes the first layer you add has no issues and can be queried for extents. I think what we can do is expose a boolean property which will determine whether this behaviour will occur or not. The default value will be false, but will be set to true by the Map Definition Editor in Maestro. If you think this is an acceptable solution, make a ticket for this on trac. - Jackie -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Problems-add-LayerDefinition-to-MapDefinition-MaestroAPI-4-0-tp7042582p7042692.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
