On Nov 10, 2011, at 22:52, Maxwell, Adam R wrote: > > On Nov 10, 2011, at 13:41, Christiaan Hofman wrote: > >> Based on my experience with automatic updating in Skim, I can say that I >> really don't like the idea. > > Gee, I can't imagine what made you dislike that idea :) > >> Even aside from the general problems involved in automatic updating, it's >> fighting against the frameworks, as they work behind our back in >> unpredictable way. So that's not gonna happen. > > As of 10.5, Apple checks anyway at save time, though maybe it doesn't play > well with Dropbox. Look for "NSDocument Checking for Modified Files At > Saving Time" at > > http://developer.apple.com/library/mac/#releasenotes/Cocoa/AppKitOlderNotes.html%23X10_5Notes > > Of course, that's right below the discussion of how they improved safe > saving, which turned out to actually break saving entirely for BibDesk on AFP > volumes. I filed a bug on that on 9 Jan 2008 and it's still open. > > -- > Adam
But the real problem is at the time when the file changes on disk. Or just after that. Or long after that. Or never. One cannot say and one cannot know when NSDocument will notice, or not. And when you make one assumption about that and NSDocument does something else, you end up with an inconsistency. So the only way this could really ever work is when the frameworks explicitly support it, because only they know what goes on behind the scenes. And that is not considering general problems involved in automatic updating, like losing pending changes. Christiaan ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
