stopClick is true, clicks handled by the feature handler don't propagate to
other click listeners; otherwise handled clicks do propagate. The same kind of
rule applies to stopDown and stopUp. These properties default to true. Thanks
to Attila Csipa for expressing the need for this feature and cooking up the
first patch. r=tschaub. (closes#1266)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5976 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
you create two select feature controls on the same vector layer, one with
hover:false that handles geometry type A only, and the other with hover:true
that handles geometry type B only, then if you click on a geometry of type A
and moves out of that geometry, the second control will unselect it. r=tschaub
(closes#1221)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5975 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
complete callback. Thus, the drag feature control won't detect a mouse-out on
that vertex and won't deactivate its drag handler. This causes errors because
the drag feature control has a feature to drag but that feature is destroyed
(feature.geometry is null). To prevent this, we make resetVertices explicitely
call outFeature on the drag feature control if the control has a feature to
drag. tschaub did most of the investigation on the problem. r=tschaub,me
(closes#1235)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5974 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
context, but the apache license requires us to mention it explicitly.
(No functional changes.)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5971 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
With this patch you should no longer see tiles loading if your layer is out of
range or not visible. Hopefully! r=crschmidt (closes#937)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5913 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
replace it was somewhat lacking. This changes the behavior such that
using hte drag handler does not totally disable text selection in IE.
Patch from Bart, r=me (Closes#906)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5911 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
adverse affect on the examples, is documented in the 2.6 release notes,
and will allow for easier display of built-in browser tooltips for
controls. r=elemoine (Closes#1303)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5907 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
MousePosition control in order to allow easier changes in formatting at
the application level (with less duplication of code). Patch from
Kleptog, r=me. (Closes#778)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5906 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
tests, examples, modification to proxy.cgi, etc. This should allow one
to build an OpenLayers based OpenStreetMap editor with some effort, and
makes it trivially simple to drop OpenStreetMap data from the API into
your OpenLayers application. r=ahocevar,elemoine (Closes#1271)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5902 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
when it should load tiles and when it shouldn't. As reported in #937
OpenLayers doesn't behave properly today, it breaks Test 1 and Test 3
of this manual test.
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5901 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
of its select feature control and passes it the current selected feature (if
any). If that selected feature is destroyed between the time it was selected
and the time the modify feature control is deactivated, the unselect method of
the select feature control will attempt to draw it on the layer while it no
longer has a geometry (it's destroyed!). This patch prevents this from
happening. Thanks to tlpinney for reporting the bug and helping on its
evaluation. r=tschaub (closes#1281)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5897 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
for following up on this, and to tschaub for reminding us of the right way
to do things. r=pagameba (Closes#1262)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5865 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
