Le 30/11/2011 10:03, Nicolas Montgermont a écrit :
Hello list,
I was wondering if the problem of the relative path of [pix_write]
under osx may be fixed soon. For reminder the actual behavior (gem
compiled this morning, used with pd-extended 0.42.5, osx.6.8) is:
- if you send no filename, you have in the terminal:
error: ERROR: -43 in GraphicsExportSetOutputFile()
error: GEM: Unable to save image to 'gem00000.tif'
- if you send a relative filename, eg. [file toto(, you have the same
error:
error: ERROR: -43 in GraphicsExportSetOutputFile()
error: GEM: Unable to save image to 'toto00000.tif'
- if you send a filename including the "~" home variable, it gives the
same error.
It only works if you set pix_write to an absolute filename inside an
existing directory, eg. [file /Users/nix/snap_pd/test (.
From what i've seen in workshop, this is a major difficulty for learners.
They are not specially used to explicit a directory from root, and
they must not have spaces in any directory name used.
It makes also a patch containing pix_write on an osx computer non
directly usable on any another ...
Is there any possibility to have relative path in pix_write under osx,
or can we imagine some workaround?
Have you tried with [getdir] as workaround ?
++
Jack
it will be of great help
thanks,
n
_______________________________________________
GEM-dev mailing list
GEM-dev@iem.at
http://lists.puredata.info/listinfo/gem-dev
