Bug 657

Summary: keymapdhtml loses navigational capabilities
Product: Chameleon Reporter: Bart van den Eijnden <bartvde@osgis.nl>
Component: WidgetAssignee: chameleon-dev <chameleon-dev@lists.maptools.org>
Status: RESOLVED FIXED    
Severity: normal    
Priority: P2    
Version: 1.99   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments: ms4w application demonstrating the problem

Description From 2004-09-02 05:50:32 
After panning in the main map the keymapdhtml widget loses its navigational
capabilities.

I will add a template which demonstrates this. I tested also with beta2.

Actions to do:
-zoomin into the main map with a box
-try to pan or zoom in the keymap, this still works
-pan in the main map
-try to pan or zoom in the keymap, this does not work anymore
------- Comment #1 From 2004-09-02 05:51:49 ------- 
Created an attachment (id=50) [details]
ms4w application demonstrating the problem
------- Comment #2 From 2004-09-03 13:27:39 ------- 
verified as reproducible using attached template.  Solution on its way (maybe?)
------- Comment #3 From 2004-09-03 16:10:55 ------- 
to clarify, the KeyMapDHTML is non-functional when the PanMap widget is selected
in the page, even on the initial page load.  As soon as you select a different
nav tool, the KeyMapDHTML becomes functional again.

Still no clue as to why ...
------- Comment #4 From 2004-09-03 16:23:16 ------- 
fixed in cvs.  The problem occurred because the PanMap code that tracks mouse
movement was unsetting the document.onmousexxxx handlers if the mouse was not
inside the map image.  The fix was for it to only unset them if they were set to
the PanMap's mouse handling functions.

I also committed a fix to the KeyMapDHTML initialization that was breaking on my
machine (no one else reported this problem ...)