Hi, Here is the explanantion of the bug discussed in user's list
This is a regression issued from a modification I did one month ago. I explain it for those interested. I set every newly created layer to featureCollectionModified=true The motivation was to warn the user that some layers are unsaved when OpenJUMP is closed The drawback is that while creating a new layer, setFiringEvent must be set to false until the layer is added to the UI I fixed that for AddDatastoreLayerWizard just before 1.3 release, but did not notice that there is also a piece of (duplicated) code to fix in AddDatastoreLayerPlugIn Setting all newly created layer to featureCollectionModified=true in the Layer class may not be the best solution for the problem I tried to fix, but setting featureCollectionModified=true in every plugins creating new layers seemed even harder to me and at this time, I have no better solution. Note that the problem may be closely related to transaction management and datastore update in OpenJUMP. Michaël ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
