Summary: | strange behaviour of MapDHTMLwidget and MapSize widget | ||
---|---|---|---|
Product: | Chameleon | Reporter: | Bart van den Eijnden <bartvde@osgis.nl> |
Component: | Core | Assignee: | chameleon-dev <chameleon-dev@lists.maptools.org> |
Status: | NEW | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 1.99 | ||
Target Milestone: | FUTURE | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: | |||
Attachments: | screendump of the behaviour |
Created an attachment (id=27) [details]
screendump of the behaviour
Sorry guys, I see it now. This is caused by using allowresize="false" on the MapDHTML widget. But maybe still this is unwanted behaviour ???
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.
Set Target Milestone to 1.99 Final
no time for this release