Sorry I missed it. I thought I searched hard enough... This new feature is already a major improvement for us, thanks!
It would be even better if XXE could notify the user when XXE (or an individual file window in XXE) gets the focus again. This is safer in the situation where the user saves the file, then the external application modifies it, then the user starts editing again. When the user saves the file, it's already too late to notify: an unsafe manual merge needs to be performed by the user at this point. If the user is notified when XXE gets the focus back, the user has a chance to reload the file before making further changes. This situation is common with a version management system (save, update, solve conflict if any, commit). 2009/9/7 Hussein Shafie <hussein at xmlmind.com> > Benoit Maisonny wrote: > > > > I'm interested in any news/forecast regarding this feature: that XXE > > would warn the user when a file has been changed on disk by another > > process and offer to reload, overwrite or save as a different name. > > > > This topic was raised last year: > > > http://www.xmlmind.com/pipermail/xmleditor-support/2008-April/006384.html > > > > This feature is critical in the context of a version management system > > where editors work in parallel on the same files (without locking). In > > some situations, not having this feature can lead to overwriting the > > changes of another user without noticing. > > > > In principle, this works as of 4.3.0 (April 10, 2009). Excerpts of > http://www.xmlmind.com/xmleditor/changes.html: > > --- > File|Save now attempts to detect whether a document stored on the local > filesystem has been modified using an external application. If this is > the case, it will report this fact to the user and it will ask her/him > to confirm that she/he still wants to save the document to its current > location. > --- > > This detection, which is inexpensive in terms of CPU usage, is always > enabled. > > > > > --- > PS: We have added this feature precisely because we have replaced the > use of system locks by application-level locks. (System locks on Windows > caused more problems than good.) > > Other excerpt of http://www.xmlmind.com/xmleditor/changes.html: > --- > Regressions: > > Local file locks (Options|Preferences, Open section, "Lock documents > stored on the local filesystem" checkbox) are no longer implemented > using mandatory, system-enforced, ``true locks''. They are now > implemented using advisory, application-level, ``soft locks''. > > In practice, this has an impact only on Windows, because the previously > used system locks were already advisory on the Mac and on Linux. > > The system locks prevented any other application from opening a document > being edited in XXE. The new application-level locks just prevent other > instances of XXE (run by you or by your coworkers) from opening the > document being edited. > --- > > > > > -- Benoit Maisonny Director & Consultant http://synclude.com Synclude -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20090907/004fb3db/attachment-0001.htm
