[PD] how to capture window-related mouse-events when toxy is discontinued?

Hans-Christoph Steiner hans at at.or.at
Wed Nov 2 16:06:37 CET 2011

On Nov 2, 2011, at 10:24 AM, katja wrote:

> Hello,
> It happens to be the case that mouse-event capturing as done by
> [toxy/tot] is crucial to my Pd performance setups. The object gives xy
> positions relative to a window, not to the screen(s). These
> coordinates are used to move GUI's around on a large xy-field, like a
> multiple-control Kaoss Pad. Specially useful in combination with
> touchscreen. Here's one clip illustrating the concept:
> http://www.youtube.com/user/instantdecomposer#p/a/u/2/Qo1CwYxmplE
> The toxy lib is discontinued in Pd-extended 0.43. Tried to find an
> alternative, asked on the Pd forum. No solution so far. I explored gem
> for GUI purposes, but this introduces even more dependencies.
> Data-structures seem an option at first sight, but can not provide
> large reactive area's (only the center pixel of an object is
> reactive). Good old [MouseState] doesn't know where the window is. In
> a brief moment of optimism, I even considered taking up maintaince of
> toxy, but the code is total hocus pocus to me.
> In the meantime, one of those live-perfo tools, Slice//Jockey, has
> started to spread around the world and is being used by some
> performers and composers. As you may understand, I am particularly
> concerned to provide a 0.43-compatible version as soon as possible.
> Any help to find a window-related mouse-capturing method, working in
> 0.42 and 0.43 alike, is very much appreciated.

Slice//Jockey is pretty awesome, by the way, I just watched the video. I think iemguts/receivecanvas will do what you need.



Looking at things from a more basic level, you can come up with a more direct solution... It may sound small in theory, but it in practice, it can change entire economies.     - Amy Smith

More information about the Pd-list mailing list