Cameron, On 10/26/07, Cameron Shorter <[EMAIL PROTECTED]> wrote: > I think it means that each button defines the mouseActions that it > responds too. Right?
Since most Mapbuilder buttons now rely on OpenLayers controls/handlers, we do not really care about the mouse actions. The addition to the existing buttons would be to add a modifier property, which would for most OL controls allow to tell if it should do its action only when eg. shift or ctrl is down while doing the mouse action. > So if I mix 2 buttons which respond to the same mouseAction into one > state, then I get a strange behaviour. > Solutions: > 1. Don't worry about it, it will only happen in fringe cases, and we can > write a new button in those cases. Either that, or -- at the configuration level -- try with a different modifier property. > 2. Allow buttons to be configured to define which mouseActions they > respond to. > > At the moment, I'd suggest 1. Relying on the OL modifiers sounds more like 2. in some cases, and in the other cases I agree with you to not worry about it (1.). Regards, Andreas. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
