code1
from Tkinter import *
root = Tk()
def callback(event):
print "i am here"

frame = Frame(root, width=100, height=100)

frame.bind("<Key>", callback)
frame.focus_set()
frame.pack()
root.mainloop()

code2
from Tkinter import *
root = Tk()
def callback(event):
print "i am here"

frame = Frame(root, width=100, height=100)
frame.focus_set()
frame.bind("<Key>", callback)

frame.pack()
root.mainloop()

code1,code2 all can run ,i want to know which one is better?
is it reasonable that frame.focus_set() is before frame.bind("<Key>", callback) or after it??
------------------ ???? ------------------
???: "Michael Lange"<klappnase at web.de>;
????: 2011?8?17?(???) ??5:26
???: "tkinter-discuss"<tkinter-discuss at python.org>;

??: Re: [Tkinter-discuss]??? bind between event and callback


Hi,

Thus spoketh "????" <1248283536 at qq.com>
Mouse events are handled differently than key events.
When you click somewhere in the window of course the window manager
"knows" which widget is clicked - the one under the mouse pointer's "hot
spot". But when you press some key on your keyboard - how would the window
manager "know" which window and which of its child widgets "is meant"?
That is where the "keyboard focus" comes in. Keyboard events are always
sent (by the window manager) to the window that has focus, where
"window" does not only mean a main application window like your Tk()
instannce, but also "child windows" as your Tkinter.Frame() .

I hope this helps

Michael


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

All your people must learn before you can reach for the stars.
-- Kirk, "The Gamesters of Triskelion", stardate 3259.2
_______________________________________________
Tkinter-discuss mailing list
Tkinter-discuss at python.org
http://mail.python.org/mailman/listinfo/tkinter-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tkinter-discuss/attachments/20110817/82cce1ce/attachment.html>