[Chris Cannam] >The assumption is that the host just passes on whatever the GUI >selects, and it's up to the GUI (which of course is provided by the >plugin author, or at least built to match the plugin) to understand >the key value pairs. Of course that means if you have no GUI you >can't use configure(), but the alternatives do seem potentially >rather complicated.
hmm. agreed of course about the complicated alternatives. i wasn't aware that a separate plugin GUI becomes nigh mandatory, which i must admit i find not to my greatest liking. however, the entire configure() liturgy makes sense once the GUI implication is accepted. i'm not too intimate with liblo/OSC, so sorry for asking an RTFM question: does OSC provide some sort of alternative, textual representation of configuration options? tim
