However, I don't like the idea of making all
controls have hard
ranges. It restricts the users in ways not necessarily intended
by plugin authors, since there's no way to set controls to values
no, it restricts users in ways EXACTLY intended by the authors.
Unless the author just intended to hint a useful range for a control
that doesn't have obvious limits. There's no way to do that if ranges
are hard.
That _CAN_ be solved, but I feel outnumbered in my position. ;) I'll bet a
pint that a lot of plugins will have internally clamped hardlimits.
Specifying
this
stuff in an API is insane.
Except on platforms that have multiple commonly used calling
conventions. (Like Win32.) If you say "use standard C calling
conventions", you're fine, but if you say nothing, you're asking for
trouble.
OK, I'm fine with that. I just don't want to see us explaining what they
are. :)