Hi Eric, I don't think we should use a renderIntent value. The main idea of the Highlight feature is to change the style of a feature only when the mouse is hover it and only that. If we change the renderIntent of a feature, when the mouse is no longer hover it, to what renderIntent we set it ? If it was "select", how do we know ? We would need to keep track of the previous renderIntent on hover.
Also, I don't see the point of "highlighting" a feature on click. The same idea goes for the fact that I don't see the point of selecting a feature on hover having HighlightFeature I can use. When you select a feature, you want to interact with it : modify, delete, display a popup that stays on screen while the feature is selected, etc. When hover, you it's only temporary. We should not remove the hover option for selecting features, but having the aboves ideas in mind I would not use a renderIntent. What do you think ? Alexandre Eric Lemoine wrote: > Hi > > As I see it: > > The HighlightFeature control is configured with a renderIntent. When a > feature is hovered or clicked, the control triggers a > "beforefeaturehighlighted" event, redraws the feature (using the > renderIntent), and trigger "featurehighlighted". > > What do you think? > > PS: I have to say that I haven't looked at Andreas' control yet. Will do. > > Thanks, > > Eric > > 2009/1/16, Alexandre Dube <ad...@mapgears.com>: > >> Yves Moisan wrote: >> >>> Having a select control and a "highlight" control >>> >>> >> Control.Highlight : that's the obvious word I was looking for the class >> name. I haven't thought about it at all (). >> >> Thanks Yves, >> >> -- >> Alexandre Dubé >> Mapgears >> www.mapgears.com >> >> >> -- Alexandre Dubé Mapgears www.mapgears.com _______________________________________________ Users mailing list Users@openlayers.org http://openlayers.org/mailman/listinfo/users