A quick thought on saving plugin settings in XML: The structure used for this should be self-contained in the XML sense and so must contain IDs. This is because the representation needs to be extensible to support complete plugin networks. I've been meaning to do this but haven't had time. Putting IDs in filenames may also be a good idea, but I think this rather depends on how the participating software wants to work with settings rather than a part of any standard. --Richard
- Re: [linux-audio-dev] saving plugin settings Kevin Conder
- Re: [linux-audio-dev] saving plugin settings Steve Harris
- Re: [linux-audio-dev] saving plugin settings Taybin Rutkin
- Re: [linux-audio-dev] saving plugin settings Steve Harris
- Re: [linux-audio-dev] saving plugin settings Taybin Rutkin
- Re: [linux-audio-dev] saving plugin settings Steve Harris
- Re: [linux-audio-dev] saving plugin settings Taybin Rutkin
- Re: [linux-audio-dev] saving plugin settings Paul Winkler
- Re: [linux-audio-dev] saving plugin settings Steve Harris
- Re: [linux-audio-dev] saving plugin settings Taybin Rutkin
- Re: [linux-audio-dev] saving plugin settings Richard W.E. Furse
- Re: [linux-audio-dev] saving plugin settings Me
