On 20 Jan 2008, at 8:04 PM, Jeremy Van Cleve wrote: > Christiaan Hofman wrote: >> >> >> But what makes you think this, i.e. how do you get the current >> file >> name? Note that auto file in 1.3.13 does not move the Local- >> Url field >> anymore, but instead works on the linked files (from the side >> pane). >> > I've been getting the file name by accessing the URL property of the > linked file. When I look at this URL in the script run by the Will > Auto > File hook, it is as expected the location of the file before it has > been > moved into my PDF folder. However, it appears that the file name that > Auto File will use once the PDF has been moved has been generated > before > Will Auto File is run; i.e. changes to fields in the publication > made by > the Will Auto File script do not seem to affect the name the PDF > ultimately gets once its been moved. The Add File or URL hook on the > other hand does seem to run before Auto File parses the format string > and accesses the required fields in the publications to later > generate a > file name for the PDF once moved since changes made to publication > fields by this script do affect what name the file ultimately gets. >
Ah, that's what you meant. That is indeed the case. And it cannot be changed. We need the generated name before trying to move, to decide if there even is a need to move anything. Also as I said changing fields just before autofiling is a bad idea. > Also, any chance the %f format specifier could get an option to remove > spaces from the field before using in a file name or cite key? > > Thanks for the help! > > Jeremy No. Christiaan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
