Sorry guys patch doesnt work! Im sticking with my own dirty hack
inside Layer.Vector drawFeature method...
On Fri, Nov 7, 2008 at 11:56 PM, Ivan Grcic [EMAIL PROTECTED] wrote:
Hey Alex...well actually i didnt catch time to try the patch...but
before patch was made i created dirty hack that was
I tried this small patch but unfortunately the problem persist. Is there
a new patch for this issue ( feature stays on screen when zooming with
mouse over it with cluster strategy ) ?
If not, I would like to disable the wheel zoom. How can I do that ?
Alexandre
Tim Schaub wrote:
Hey-
Eric
Hey Alex...well actually i didnt catch time to try the patch...but
before patch was made i created dirty hack that was working for me.
Its not the best solution, but hey it works :)
inside drawFeature just add one if statement
function(feature, style) {
if
Hi,
made a new post on on 1782, cuz its probably same issue:
http://trac.openlayers.org/ticket/1782#comment:4
You can remove/add SelectFeature on checkbox.
Regards,
Ivan
On Tue, Nov 4, 2008 at 5:43 PM, Andreas Hocevar [EMAIL PROTECTED] wrote:
Hi,
to me it seems this issue is at least related
Hey-
Ivan Grcic wrote:
Hi guys,
another strange behavior, with similar issue. Features that are not
spuppose to render are rendered!
Im loading my vector feature from gml file, containing 21 features
that are Polygons or MultiPolygons. When you zoom in, lets say on
north part of map,
Hi,
to me it seems this issue is at least related to
http://trac.openlayers.org/ticket/1782, probably it is the same issue.
Ivan, can you please check if the described problem persists when you
remove the SelectFeature control?
Thanks,
Andreas.
On Tue, Nov 4, 2008 at 5:07 PM, Tim Schaub [EMAIL
Hi guys,
another strange behavior, with similar issue. Features that are not
spuppose to render are rendered!
Im loading my vector feature from gml file, containing 21 features
that are Polygons or MultiPolygons. When you zoom in, lets say on
north part of map, features from south are sometimes
Hi.
Yes, this looks like a bug in OpenLayers.
I'm under the impression that this isn't a bug in the cluster strategy
but either in Layer.Vector or in Control.SelectFeature. Indeed, I
think SelectFeature calls layer.drawFeature on feature
selection/unselection without checking whether the feature
Yup, its not Cluster Strategy...
http://trac.openlayers.org/ticket/1806#comment:2
On Mon, Nov 3, 2008 at 9:11 AM, Eric Lemoine [EMAIL PROTECTED] wrote:
Hi.
Yes, this looks like a bug in OpenLayers.
I'm under the impression that this isn't a bug in the cluster strategy
but either in
OK... i found it..inside Layer.Vector...now the question is: should i
put something like this:
if (OpenLayers.Util.indexOf(this.features, feature) != -1){
inside drawFeature: function(feature, style) {
or inside every other function inside Layer.Vector that uses
drawFeature function?
When I
Hey-
Ivan Grcic wrote:
OK... i found it..inside Layer.Vector...now the question is: should i
put something like this:
if (OpenLayers.Util.indexOf(this.features, feature) != -1){
inside drawFeature: function(feature, style) {
Nope. Making drawFeature that safe at the expense of iterating
Yes. Especially since drawFeature is often called from addFeatures,
where we're assured that the feature is in the layer. So, instead, we
may want to change the select feature control so that it calls
drawFeature only if, in the case of selection, the feature is in the
features array, and in the
Hey-
Eric Lemoine wrote:
Yes. Especially since drawFeature is often called from addFeatures,
where we're assured that the feature is in the layer. So, instead, we
may want to change the select feature control so that it calls
drawFeature only if, in the case of selection, the feature is in
Tim, what about this case: feature is selected then is *removed* from
the layer. Eventually the feature handler triggers mouseout, which
makes the select feature control call drawFeature for a feature which
isn't in the layer. Eric
2008/11/4, Tim Schaub [EMAIL PROTECTED]:
Hey-
Eric Lemoine
Eric Lemoine wrote:
Tim, what about this case: feature is selected then is *removed* from
the layer. Eventually the feature handler triggers mouseout, which
makes the select feature control call drawFeature for a feature which
isn't in the layer. Eric
layer.removeFeatures sets feature.layer
Was trying to reproduce this on normal gml/wfs layer, but obviously
theres not such problem
because we are always dealing with fixed number of features. So, when
one zooms in while
feature is selected that feature is also rendered on next zoom,
because it exist on all zoom levels
In cluster
16 matches
Mail list logo
