Re: [Plib-devel] LoadASE problem.

[Dave M. <dp...@ef...>]

Steve Wrote :

>  Your ssgParser/ssgLoadASE/ssgSaveASE code is a bit brutal when
>it finds an error.  If I try to load or save a file that does not
>exist, it does an 'exit(1)'!!! Eeeekkkk!
>
>  That's kinda brutal when you've just spent 3 hours building a
>model in PPE - and when you try to save it and accidentally open
>a write-protected file or a non-existant directory *KABLOOIE*!!!
>
>  Please have ssgLoadASE return NULL if it can't load a file
>for *any* reason - and have ssgSaveASE return FALSE if it can't
>save.
>
>  This is kinda urgent!
>

understood. i'll work on that today

>  Also, the _ssgMakePath function chops off the leading path
>information or something...we need ssgModelPath to be applied
>consistantly across all loaders.  What ssgLoadAC does is:
>
>  * If the path starts with a slash - use it as-is.
>  * If the path starts with anything else, prepend _ssgModelPath
>    and a slash.
>
>  I'm not sure if that's the *perfect* rule - but it's what existing
>applications expect.
>
 
this is an argument for the file system wrapper
different OSes use different seperators and also i get ASE files
with texture names that all start with backslashes and i don't want
to recreate the directory structure on the modeler's machine.

i'm attaching a spec proposal for a PLIB virtual file system.  It is very similar
to what is used in crystal space.  Feedback?

--Dave