Hi Al,
> It works after a fashion, but my problem is this: in > FeatureSelectHandler.onSelect/onUnselect, I catch the mouseover and mouseout > events. In the methods you are referring to, the Mapbuilder events "mouseoverFeature" and "mouseoutFeature" are fired. Your custom widget should listen to those events. This has the advantage that both events have a parameter holding the feature id (fid) of the feature, from which you can determine the information you want to show. > The problem is that the mouseout event is fired immediately after > the mouseover event even thought the mouse does not move. It has been awhile > since I have been this deeply immersed in javascript, so I don't know if it > is a basic event processing problem or not. I am only working in Firefox > 2.0. I am wondering if it has something to do with the > OpenLayers.Geometry.Point/Vector object not having any bounds? The events you are referring to are fired by the SVG/VML renderer of your browser. If you have a custom widget that listenes to the mousoverFeature and mouseoutFeature events of Mapbuilder, you should not experience this behaviour. > If I can get this "hover" functionality to work with just config file and > xsl file customizations, I think it will greatly add to the pool of > potential MapBuilder users - namely all the business apps for which > geospatial viewing would be an extremely nice feature, but for which GIS is > not the primary focus. I would be glad to submit a diff of what I have done > (here or how?) Sorry if I am hitting you with stuff that is not on the > critical path. I just wanted to see if this happened to jive with what any > of you developers were working on. My idea, which I had no time to implement yet, was to give GmlRendererOL another config property (mb:featureOnHover), which will be handled by another TipWidget. For this, TipWidgetOL can be used, but with a new method (eg. onMouseover) similar to onClick. In GmlRendererOL/init, this method should be bound to the mouseoverFeature event. Another method, eg. onMouseout, should be bound to the mouseoutFeature event. Of course, the popup handling stuff should then be moved from onClick to a common method also to be used by onMouseover. This should be all that is needed. A diff would be greatly appreachiated, if you are willing to implement that. Regards, Andreas. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
