Re: The Plugin Settings Approach.
Re: The Plugin Settings Approach.
- Subject: Re: The Plugin Settings Approach.
- From: Jay Vaughan <email@hidden>
- Date: Wed, 12 Feb 2003 16:07:33 +0100
OK, but this does have a number of practical problems as well:
1) If the user copies the session file to another computer without copying
the plug-in settings files, they cannot open the session properly (e.g. The
session is not self contained).
Yes, okay, I see the problem with this ...
2) If the hash changes for some reason the link breaks -- any number of
unexpected events could cause this to happen.
Such as? The user changes the name of the file in Finder, perhaps?
3) If you change the contents of the preset later, it will in-advertently
change one or more sessions (silently). This is a huge problem. If this is
avoided by having unique setting files for each session, the management of
the settings becomes the users problems.
Well, the point is I'm trying to avoid having the user deal with
managing the plugin settings stuff.
I see the pro's to the existing approach, sure, anyway. Lets drop it I guess.
--
j.
Jay Vaughan email@hidden
>>music:technology:synthesizers - www.access-music.de/
_______________________________________________
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.