Guilherme Polo <[EMAIL PROTECTED]> added the comment: The "tab" key is bound globally to move the focus to the next widget, but that is not what you would want for a text widget. So, text widgets breaks the natural flow of tab key events to achieve this, and, when you specify bindings like that (in your "not ok" example), it stops your widget-level binding from firing.
I don't see anything to be fixed here, so I'm closing it. ---------- nosy: +gpolo resolution: -> invalid status: open -> closed ____________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue429031> ____________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com