I believe that the only obvious ones are ints that are truly ints and
string parameters. For floats, you have the issue of display precision.
Take, for example, frequency. Not probably useful to display 20.00000000
Hz. The plugin would know that it was frequency and should have 2 digits
of precision past the decimal.
Mike
Tim Hockin wrote:
On Mon, Nov 08, 2004 at 09:01:37AM -0700, Mike Berry wrote:
I think we need all three as requirements. However, note that the third one is optional for the plugin to support. I think that #1 is a requirement for all plugins for all non-opaque parameters. #2 and #3 are optional for plugins.
Why should #1 be required? It should only be required for non-obvious parameters. Usually 3 = "3", right?
I guess this goes back to a default implementation and overriding a method (C++ speak - though we kinda said C for the API :)
Updated:
http://www.gmpi-plugins.org/gmpi/requirements.php
Tim
---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
-- Mike Berry Adobe Systems
---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
