Modify ↓
Ticket #22 (new enhancement)
More points for curves filter
| Reported by: | ttill | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | version 1.2 |
| Component: | filter | Version: | 1.1 |
| Keywords: | Cc: |
Description
It would be great to have more points in the curves filter. As there is no array param maybe F0R_PARAM_STRING could be used to store a "unlimited" list of points.
Attachments
Note: See
TracTickets for help on using
tickets.

I understand the desire to keep the API simple and not include complex types, which is why any plans to introduce a more complex parameter type is being rejected. I would suggest that some plugins include both a reasonable amount of enumerated floating point parameters as does curves. This will allow it to work with most existing applications or ones that provide generics UIs. Then, it could add an additional string parameter to pass a much more complex set of parameters for those applications that want to provide plugin-specific UIs and leverage advanced capabilities. I think this approach provides a good balance in the meantime. If this situation grows, then there will obviously be demand for some change.