On 31.12.2007, at 00:21, Christiaan Hofman wrote:
>
>
> We save the file using an alias with relative path information.
> However during a bibdesk run we also keep another type of reference
> as the main link to the file (however this type of reference cannot
> be saved). Relative aliases require the two paths involved to be on
> the same volume, so that 's where it probably goes wrong. However
> it's still possible to link files across volumes, because we actually
> work with the other type of reference. But tracking it when it moves
> can get broken. I'm not sure where precisely things go wrong and how
> to catch problems. But it sure should get fixed somehow.
>
> Christiaan
>
> The problem is in fact with the other reference. Between disks files  
> are not moved but copied, so the file reference loses track of it.  
> I've added a workaround that updates the file references after auto- 
> filing for the next nightly. But this requires more testing, also to  
> see if the aliases work correctly with external disks (especially  
> important between saves and  also when using relative paths).

Just tested the latest nightly, and now autofiling on an external disk  
works. Didn't do serious testing, but following the steps I posted  
works now.

The live web display is also cool.

simon
--
Simon Spiegel
Steinhaldenstr. 50
8002 Zürich

Telephon: ++41 44 451 5334
Mobophon: ++41 76 459 60 39

http://www.simifilm.ch

„In a world getting more and more democratic, film directing is the  
last resort for dictators.“ Francis Ford Coppola




-------------------------------------------------------------------------
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

Reply via email to