Aubin Paul wrote:
> Would it be possible to have the code write the FXD to the vfs only?
Sure: check if folder.fxd is in current dir, take it than. If not use
vfs.getoverlay to get the correct name. But please make it possible to
switch this on/off.
> Also, would it be possible to put the embedded id3 image in there?
put it as folder.png in the dir or overlaydir.
> What would be nice is to have the img go into the vfs, same with the FXD file;
> I imagine a lot of people on read-only media would appreciate that.
That's not the point. The vfs code checks if it has write access to
folder.fxd. If not, it takes the vfs as default. So now, you get a
folder.fxd in the dir and if that's not possible, it will go to the
vfs. That's why I wrote it :-)
If you use vfs.open to store the image, you will also have a fallback
to the vfs if folder.png can't be saved.
Dischi
--
I do not fear computers. I fear the lack of them.
-- Isaac Asimov
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Freevo-cvslog mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-cvslog
