Not the best solution, but you may be able to monitor a slider for value changes to emulate a click-down, click-up situation... so you'd be tricking a click-drag :)
fdch.github.io
> On Mar 14, 2019, at 11:02 AM, IOhannes m zmoelnig <zmoelnig@iem.at> wrote:
>
>> On 14.03.19 10:42, Chris McCormick wrote:
>>
>>> keep in mind that it is not touch sensitive.
>>
>> What do you mean by this? It only responds to mouse events and not touch
>> events?
>
> no. that's not what i meant.
>
> it was a(n admittedly stupid) joke on the discrepancy between a
> mouse-based interface (where you only get a boolean value of whether a
> button is clicked or not) and the expectation of a (musical) "hardware
> keyboard" that typically gives you "touch sensitive" data in the form of
> 'velocity'.
>
> fgamsdr
> IOhannes
>
>
> _______________________________________________
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list