Re: Introducing support for ShuttlePRO v2

::do_request() is a mechanism for cross-thread signalling. It should
probably not be used explicitly in any control surface code. It allows one
thread to arrange for another thread to do something (possibly to stop
running, or execute some closure, or whatever ...)

There are no abstractions except actions that can be used for
configurability at this time. What would be an example of the sort of thing
you want to make configurable?

On Mon, May 29, 2017 at 7:55 AM, Johannes Mueller <
[email protected]> wrote:

> Hello,
>
> I am working on a control surface to support the ShttlePRO v2 device [1] on
> Linux. The device is working well using the input event struct of linux/
> inputs.h.
>
> By now the handling of the events is hard coded and doing things that make
> sense to my work-flows. However I'd like to make it user configurable
> although I am not sure how to do it exactly (how to configure things that
> are
> not actions, for example).
>
> But to begin with I have a question regarding the ControlProtocol API:
> What's
> the deal with void AbstractUI<RequestObject>::do_request(RequestObject*)?
> I
> had to implement it to make my class instantiatable, so I just copied the
> code from OSC::do_request() without actually knowing what it means. Can
> someone give me a hint, please?
>
> You can take a glimpse on the code on
> https://github.com/Ardour/ardour/compare/master...
> johannes-mueller:shuttlepro
>
> Any other hints welcome.
>
> Thanks
>
> Johannes
>
> _________
> [1]: http://www.contourdesign.com/UK/product/shuttlepro-v2/
>
> --
> https://github.com/johannes-mueller/
> _______________________________________________
> ardour-dev mailing list
> [email protected]
> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org
>

_______________________________________________
ardour-dev mailing list
[email protected]
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org