[Tkinter-discuss] Event debugging

Michael Lange klappnase at web.de
Thu Dec 20 17:46:59 EST 2018


On Thu, 20 Dec 2018 14:47:39 +0000
Vasilis Vlachoudis <Vasilis.Vlachoudis at cern.ch> wrote:

> Simple print doesn't work, since I don't get the call.

Ok, then it does not seem to be another widget that intercepts the event.

> Unfortunately when I try to simplify and isolate the widget it I cannot
> reproduce it. It only appears in the whole application.
> I've tried to bind also the Button-1, Release-1 and Button-2,
> Release-2, Double-2, 3 I get all the Button/Release calls, but I don't
> get any Double-X call at all.
> Its a bit strange behavior, I have a big nesting of frames and
> PanedWindows... .!flair.!flairtabribbonframe.!treesplitter.!frame.!
> frame2.!panedwindow.!frame.!filestab.!panedwindow.!frame.!
> colormultilistbox.!panedwindow.!frame.!exlistbox
> If I remove the grand parent PanedWindow and Frame (just above the
> colormultistbox) then it works ok. However it is not the PanedWindow
> since I replace it with a Frame then it doesn't work. It seems it works
> if I remove two nestings.
> Could it be some result of big nesting of widgets.

Did you try to write a minimal example app with the same
stack of nested widgets?

> Still same version of the code on Fedora it works.

Maybe a WM / DE issue? Did you try some other DE's with Ubuntu besides



.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Conquest is easy. Control is not.
		-- Kirk, "Mirror, Mirror", stardate unknown

More information about the Tkinter-discuss mailing list