Hi, > Has this been discussed earlier? If shapefile is opened OJ >>> it seems to keep it open even if the layer is deleted from a >>> project or even if the whole project is closed. Only way to >>> free shapefile for example to be deleted is to close the whole OJ. Cannot reproduce this behaviour. >> In practise it would be bad is someone edits a shapefile on a network >> drive if someone else has it open in OpenJUMP on another computer. Or >> even if it is open in another program on the same compurer. > true, but current implementation should be as described, just checked the > code. If a test confirm that a file is kept locked until OpenJUMP is closed (even after the layer and associate tables are completely removed from project), I agree this can be considered as a bug.
Between the moment a source is loaded and the moment it is released (layer removed, project closed...) I think I would prefer the file to be locked. But it probably does not work like this at the moment, and it may not be so trivial to implement (needs to check when all resources are released, including table views...). Michaël > >> But once it is removed from all tasks/projects there should be no reason to >> keep it open. >> > would be elegant, but see above. Windows does some locking if files reside on > network drives, but usually it is up to applications to take care of that. > usually file datasources are read as whole and written as whole. if that is > not the case, they are kept open for writing and locked by that. > > as far as i can see shapefile code does the standard procedure here. > > let's wait if someone can reproduce it and file a bug then. > > regards ede > > ------------------------------------------------------------------------------ > Using storage to extend the benefits of virtualization and iSCSI > Virtualization increases hardware utilization and delivers a new level of > agility. Learn what those decisions are and how to modernize your storage > and backup environments for virtualization. > http://www.accelacomm.com/jaw/sfnl/114/51434361/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > ------------------------------------------------------------------------------ Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
