Thanks Andrea, I will grab it this evening and push up a SNAPSHOT for your testing.
I did not make any progress on the tools deadlock (beyond what was discussed with Maurcio in December). Next step for me is to check the history of the involved classes. My prime suspects are: - Blackboard (this is where the deadlock is occurring) - EditFeature (this is the class that was introduced to make form work easier) As with most deadlocks the strategy is to: 1) find the deadlock - check the stack when tool changes the blackboard, and go through the stack and write down what objects were locked (and in what order) - find who else is holding a lock (and they *must* of accessed the objects in a different order 2) resolve - sort out which order of access is correct, and ensure both parties follow that order - short term: write it down the order in javadocs - long term: look if the power to deadlock can be taken away (via forcing both to use the a command or something) -- Jody Garnett On Monday, 14 January 2013 at 12:14 AM, andrea antonello wrote: > Hi Jody, > you kind of voluntared for the geoscript pull request. > > Here it comes: https://github.com/uDig/udig-platform/pull/164 > > Code and first docs should be fine to get started. > > Cheers, > Andrea > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel > >
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
