Re: Filing of User Presets - files vs. builtin
Re: Filing of User Presets - files vs. builtin
- Subject: Re: Filing of User Presets - files vs. builtin
- From: Marc Poirier <email@hidden>
- Date: Sat, 26 Oct 2002 01:44:50 +0200 (CEST)
>
The way I read it, all but option 0 (my favorite!) don't include user
>
interaction in the save/load phase... in these proposals, this is
>
handled 'automagically' (yark). There was talk of putting multiple
>
presets into some opaque preferences file! And then talk of
>
'exporting' if you wanted to share them! Absurd!
>
>
But, if I read it wrong, and these schemes are only in _addition_ to
>
sensible preset management, then I guess I've got nothing against it.
>
Except that it's stupid.
Well, stupid to you, I guess... For me personally, I like it. You know,
just like in Logic, how you can save presets into
{appfolder}/PluginSettings/{pluginname} and, if you do that, Logic will
automatically construct a dropdown menu of those presets (with submenus
for subfolders) for that plugin whenever you load an instance of it. I
like that. With the way I work, it's nice. If that idea could be
extended so that any app could choose to do what Logic does, if I put the
files in a certain location, I'd like it even more. When you save a
preset in Logic, the file save dialogue defaults to starting you off in
the "official" location. But if you want it elsewhere, you just navigate
elsewhere. Works fine for me.
So in summary, I like that, which either means that I am stupid or that I
like stupid things. But I guess some other people like it too, and that's
why we're talking about it.
But I'm with you on the opaque preferences file with export/import
options, I don't like that.
Marc
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.