I think this is a good idea, but don't know in detail how to do it. Patches should be able to have a say as to what they "prefer" (beyond what's available via the declare object) but they can't just smash over everything - for instance, they might not know what audio device they should use.
O've started putting local config files in some of my patches for which I have versions for 3 different audio setups the patch has to run in - I just use loadbang and textfile :)
Miller On Thu, Apr 09, 2009 at 12:56:09PM +0200, IOhannes m zmoelnig wrote:
hi all.
i was wondering what the status of "embedded preferences" (that is: using a local preference file that is attached with a certain Pd-application rather than the global preferences valid for all Pd's on the system) for all platforms and the various tastes of Pd was.
i know that you can embed a preference file in an osx-bundle in Pd-extended (at least since 0.40), and iirc this embedding has been accepted into Pd-vanilla as well (since version ?)
i seem to remember that a similar mechanism exists on linux.
i cannot remember anything about w32 (which might be more complicated, given that with w32 we are using the registry rather than a file that ships with Pd)
so my question is:
- is embedding preferences supported on all platforms?
- is embedding preferences supported on both Pd-vanilla and Pd-extended?
- what is the minimum version of Pd i need to acquire the usufruct (with
regard to taste)
fgamdsr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list