[PD] how to capture window-related mouse-events when toxy is discontinued?
jancsika at yahoo.com
Sat Nov 5 16:20:11 CET 2011
----- Original Message -----
> From: Mathieu Bouchard <matju at artengine.ca>
> To: Jonathan Wilkes <jancsika at yahoo.com>
> Cc: katja <katjavetter at gmail.com>; "pd-list at iem.at" <pd-list at iem.at>
> Sent: Saturday, November 5, 2011 10:41 AM
> Subject: Re: [PD] how to capture window-related mouse-events when toxy is discontinued?
> Le 2011-11-02 à 08:19:00, Jonathan Wilkes a écrit :
>> One thing is that any GUI objects created with [widget] cease to pass
> messages when the containing window gets unmapped.
> Is that a problem...? What problem does that cause ?
Well, if you threw a [tgl] into a subpatch or abstraction, got the object chain that it's in working,
then closed that window and the [tgl] no longer passes messages, it is extremely likely that your
patch will no longer work.
Granted one might be less likely to be embedding [widget] objects where they won't be seen, but
that requirement limits their usefulness. For example, I can send a "set" message to a [tgl], or change
its color when it's unmapped-- not only can I not do that with [widget], but I'll get an error if I try.
At least that's what I remember the last time I used [widget]. It also didn't [loadbang] properly which
> Anyway, Pd does weird things with unmapped window... It deletes all canvas-items
> whenever you minimise a window. I don't know whether it was ever useful to
> save RAM back in 1995 when 16M would cost between 640 $ and 2000 $ (remember the
> RAM shortage racket ?), but this behaviour is part of Pd, and you have to take
> into account, whether you use t_widgetbehavior or Toxy.
> I don't remember whether DesireData preserved that behaviour, but it's
> possible that I didn't bother changing that (however, DD introduced
> additional layers so that C code would hardly know what Tk is).
> | Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
More information about the Pd-list