You need to log in before you can comment on or make changes to this bug.
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
Created an attachment (id=50) [details] ms4w application demonstrating the problem
verified as reproducible using attached template. Solution on its way (maybe?)
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 ...
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 ...)
