Hi Krzysztof,
btw, Thomas, have you got any reply to this? I would need to find a way of getting info from the gui layer, first in order to clone MouseState and mousefilter, then, possibly, with some other clones too -- although for mouse classes I would probably use a by-request method (polling), using something like "winfo pointerxy".
No, no reply.... so i'm trying to get from pd what i can without having to use bad/non-portable tricks. That is: - key down and up .... this is generally really dirty stuff in PD, there are no scan codes in TCL/TK, just ascii and extended key names - mouse down and mouse dragging (also outside the object rectangle) - idle mouse position
I don't know if there is a way to get the TCL/TK mouse state by polling, there seem to be just mouse events... but that's not too bad - one can cache the info.
Yet I do not fully understand your code examples. With replacing tcl/tk bindings of gui events to a canvas (those defined in pd.tk), do you mean a canvas containing your gui object, or a canvas created by that object? If the former, are you going to pd_bind your gui object to the same symbol a containing canvas is bound to (declaring a dummy anything method, I guess)? Or, rather, pd_binding to a different symbol, then resending the gui messages you got in your object, up to a containing canvas?
These were just examples how PD itself could make use of all the possible information. Looking at PD.TK this is not fully exploited. I can hardly use these code fragments for flext as they would intercept all TCL/TK events. Resending them or modifying PD.TK seems to be non-portable to me as it is very likely to collide with other externals making use of such tricks.
Generally i have to say that i'm (after a short recovery) more and more fed up with TCL/TK. Although it's not a bad system i consider it unsuitable for a multi-media environment. It's a dead-end street. Just had a deeper look at Max/Jitter. It's just incredible.
greetings, Thomas