On Oct 10, 2007, at 04:10, Christiaan Hofman wrote: > Apparently bibdesk clears the change count when exporting. That's > wrong, so I changed that. However the remark mentions that it is > necessary because of finalizing changes (probably due to the > BDSKFinalizeChangesNotification?) I don't really understand that: > why does it necessitate clearing the change count?
Looking back through my bibdesk-commit archive, it shows up on 14 August 2005 (your commit!). The log message was "Finalize changes before writing data. Clear the dirty flag after a delay when saving to file, as the undoManager can flag the doc as dirty with a delay." Does that sound familiar? I vaguely recall this, so maybe there's something in the list archives too. -- adam ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bibdesk-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
