Hi. Still i'm not convinced the problem is related to the pixel limit.
When the layer is back to in range i tend to think that this.left and
this.top should be reset to zero, which isn't the case today because
from the renderer perspective it's like resolution has never changed.
One way to solve
I have a patch that i'd like you to test. I cant post it right now but
will do as soon as i can. Cheers. Eric
2008/7/29, Eric Lemoine [EMAIL PROTECTED]:
Just checked: zoomChanged is set to true in moveTo when coming from
setVisibility(true), so the fix describes in my previous email might
just
Thanks Eric,
I'll test your patch as soon as it's ready.
Alexandre
Eric Lemoine wrote:
I have a patch that i'd like you to test. I cant post it right now but
will do as soon as i can. Cheers. Eric
2008/7/29, Eric Lemoine [EMAIL PROTECTED]:
Just checked: zoomChanged is set to true in
On Tue, Jul 29, 2008 at 4:48 PM, Alexandre Dube [EMAIL PROTECTED] wrote:
Thanks Eric,
I'll test your patch as soon as it's ready.
I attached it to http://trac.openlayers.org/ticket/1631. It is untested.
--
Eric
___
Dev mailing list
Hi Eric,
I opened a ticket : #1631.
Of what I understand, the bug comes from the resolution and inRange
value of the layer. While it's not inRange, our renderer doesn't change
its left and top values, even if we zoom. But, when inRange, it first
checks the resolution. If it changed,
On Mon, Jul 28, 2008 at 3:35 PM, Alexandre Dube [EMAIL PROTECTED] wrote:
Hi Eric,
I opened a ticket : #1631.
Of what I understand, the bug comes from the resolution and inRange value
of the layer. While it's not inRange, our renderer doesn't change its left
and top values, even if we
Hi Eric,
The location is correct. It is ok to have a 15000px limit and that
works perfectly.
To fix the bug, I think when the code checks the resolution, if it's
the same than before, it should also check the location of one of our
feature position... If it's near our 15000px limit (
