I probably should have asked for the .projectRegistry. Since I don't know what is wrong it is hard to debug. Of course if we detect that error we could probably have uDig delete the file and re-try.
Jesse On Tue, Jun 7, 2011 at 8:52 AM, andrea antonello <[email protected] > wrote: > Jesse, > do we have any way to avoid this? Is it possible to trap such a > situation and tell the user that the workspace is corrupted and maybe > try to load only what it is able to load? > > I have another user reporting such an issue and people are simple > stuck in front of this problem. > > Andrea > > > On Mon, Jun 6, 2011 at 12:17 PM, Daniele Andreis > <[email protected]> wrote: > > Hi Jesse, > > > > Thank you for your reply, I have deleted the .projectRegistry file, > > and then all work well. > > > > thanks and regards > > > > 2011/6/6 Jesse Eichar <[email protected]>: > >> could you: > >> > >> shutdown uDig, > >> rename your workspace > >> restart uDig and see if you still have problems. > >> > >> If that works then try: > >> > >> back up your workspace > >> delete the .projectRegistry file > >> Open each project one at a time until you find one that has a problem. > (or > >> perhaps just deleting the .projectRegistry will fix the issue) > > > > > > > > > > -- > > Daniele Andreis > > _______________________________________________ > > 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 >
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
