Hi Matthias,
thanks for sharnig your code/plugin. Unfortunately I don't have the
time for a deeper insight into it know.
But in august/september I will have to implement my
communication-bridge. So maybe I will contact you again.
Nils
Matthias Scholz schrieb:
Hi,
you can download my
Michaël Michaud wrote:
Hi,
I've noticed that (for quite some time now) newly loaded feature
collections/layers are now considered modified by default. I've been
using that check in the WFS plugin to enable the update button only if
the layer is actually modified. I've added a workaround
Hei Larry,
thanks!
I will do some further testing when I find time. Now I just have use
thrad.sleep(30) to give it some time...
Probably I will have a look then at SkyJUMPs RenderingManager.
cheers,
stefan
Larry Becker wrote:
Hi Stefan,
The JUMP rendering architecture was never designed
I'm not sure it helps, and I haven't tried it on WFS layers, but
theoretically my select all modified features plugin distinguishes between
newly created features and features loaded from a dataset.
Larry
On Fri, Jul 9, 2010 at 3:11 AM, Andreas Schmitz schm...@lat-lon.de wrote:
Michaël Michaud
Hei Andreas and Michael,
playing save is what we should do.
For creating new layers I am most often using context.addLayer() - so
why not adding the flagging there instead of changing all plugins?
An option would be to create a second addLayer() method with a boolean
parameter for flagging if
Dear Larry,
Could you tell me how it works? It seems a loop is required for continous
update an attribute. How can it be replaced by a event handler?
Thanks,
Elton
--- On Fri, 7/2/10, Larry Becker becker.la...@gmail.com wrote:
From: Larry Becker becker.la...@gmail.com
Subject: Re: [JPP-Devel]
Hi Elton,
Make your loop variable a class variable. Have the loop control and
attribute update inside the event handler. While the loop is still going
invoke the event handler again, also from within the event handler. Once
you have set up the event handler and invoked it once, just fall off
