Well you are right. All the startup flags can be used to do your own config file in a batch.
But for example in the config file there could be a deken dir. So here we do 2 things, Set the any/user/friendly/path for externals and add it to Pd search path. Also by doing that, some auto-search can be excluded and there are less “file not found, next in the?” All %appdata% %useprofile% are avoided. You can say is a bit redundant, but a config file is more user friendly, and more flexible than the windows registry. There were reports on windows that preferences get lost. This is most likely a win.registry.shi*, and it takes time to prepare again all that you did using Pds preference, path, lib, etc. Alex, Roman, and Dan also mentioned the OSX troubles. Also we can do different startups by selecting which config file to use. Or by simply manually changing its name. Mensaje telepatico asistido por maquinas. ________________________________ From: Pd-list <[email protected]> on behalf of [email protected] <[email protected]> Sent: Friday, February 17, 2017 10:12 PM To: [email protected] Subject: Re: [PD] deken and windows On 02/17/2017 11:07 PM, Lucas Cordiviola wrote: > I think that the config file is something that's becoming a “Must” . don't we have config "files" on all platforms? (on w32 it is hidden in the registry, but i don't see anything that couldn't be configured there as well). but the more important question is: what is the configuration file going to solve and how? (esp. what changes to the configuration file do you envision that will make these things possible?) gfasd IOhannes
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
