[Chameleon-dev] [Bug 353] strange behaviour of MapDHTMLwidget and MapSize widget

bugzilla-daemon at www.maptools.org bugzilla-daemon at www.maptools.org
Fri May 21 10:19:42 EDT 2004


------- Additional Comments From pspencer at dmsolutions.ca  2004-05-21 10:19 -------
um.  There seems to be a link between this behaviour and bug 375, they both seem
to relate to problems that happen because the map size is different between the
map file and the MapDHTML widget.  Although in the other bug, I think
allowresize was true so you didn't see this particular bug there.

Looking a little closer at the code reveals that MapDHTML widget should set the
map size in the ParseURL function, and this is executed with high priority so it
should happen before most other widgets ParseURL.  The ROIRectangle tool only
grabs the map size in the GetJavascriptFunctions call, which happens after all
ParseURL function calls.  So by that point, all changes to the map object should
have happened and all widgets should be working from the same set of parameters.
 I'll do some searching through the code to see if any widgets access the map
widget/height in functions that get called before ParseURL.

The only other thing I can think of is that there is some kind of reference
problem with the map object, which would be very strange but could happen.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the Chameleon-dev mailing list