[Mapguide-trac] [mapguide-trac] #2086: Maestro API - RuntimeMap DataExtent is Not Dynamic

[MapGuide Open Source]

#2086: Maestro API - RuntimeMap DataExtent is Not Dynamic
----------------------------+-----------------------------------------------
   Reporter:  crispinatime  |       Owner:  jng        
       Type:  defect        |      Status:  new        
   Priority:  medium        |   Milestone:  Maestro-5.0
  Component:  Maestro       |     Version:             
   Severity:  major         |    Keywords:             
External_id:                |  
----------------------------+-----------------------------------------------

Comment(by jng):

 Try this:

  * Load the .net Developer Guide's sample (this assumes you enabled this
 feature during installation)
  * Load the '''Modifying Maps and Layers''' sample
  * Click '''Map Information''' to bring up mapinfo.aspx in a new window.
 It reports on the current state of the MgMap.
  * Observe the data extents.
  * Zoom/Pan to a different area of the map
  * Click '''Map Information''' to bring up another mapinfo.aspx window.
  * Observe that data extents.

 If it's like what I saw, the data extents '''remains the same''', and this
 is from the official MgMap class! If we look at what what actually calls
 MgMapBase::SetDataExtent() to modify the data extents, it's only the
 controller class for the (now defunct) DWF eMap viewer. Meaning nothing
 actually uses this particular extent. All rendering operations are driven
 off of center/scale/width/height/dpi

 So in that respect, the value you're seeing matches official MgMap
 behaviour, which gives the same data extents everytime as well.

 What it all boils down to is: If this is a defect, the official API has
 this defect as well and it should be fixed there as well. Probably should
 discuss on -internals first.

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/2086#comment:1>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals