On Nov 26, 2007, at 3:51 PM, James Owen wrote: > 0.93 now works great, and no longer exhibits the can't copy file > problem. > > I ran it once, It worked. I reran it without deleting the -bib.pages > file, and a -copy.pages > file appeared, and the copy error message appeared. Then I deleted the > -bib and -copy.pages > files, and ran it a third time, and this time it worked. Is this > expected behaviour?
Great. Actually, the intended behavior is for the script to trap the duplicate file name error and present a dialog with two alternative buttons. One button moves the conflicting (older) file to the trash and continues the script, and the other leaves the files as they are and aborts the script (deleting the new duplicate). This happens in Tiger, but in Leopard this error is not caught in the script and the dialog is not presented. This leads to a subsequent error, which does stop the script (without altering any files) but leaves behind the new duplicate. So it works OK, but it's less elegant than it should be. One other minor problem I'm seeing in Leopard is that the feedback text box in Pages (the green box) is specified in the script as not having word wrap, but it does anyway. This shoves the text around a bit while the box is showing--a cosmetic issue only as the text collapses back to normal when the box is deleted. Again, this is more elegant in Tiger where the box just sits above the text without affecting it (the intended behavior). I'll be looking to fix these minor issues as Leopard develops. Jim Harrison UVa ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
