[issue28264] Turtle.onclick events blocked by Turtle.stamp
George Fagin added the comment: Now you've got it. Clicking on the turtle results in an event message - at which point I spin the turtle and issue the message to make it clear that the message arrived. However, if you try doing that after a 'Turtle.stamp()' the message never comes. Issuing any of the other commands with the buttons will address the problem. This is why I think it's related to z-order: by doing something else the turtle gets focus again, and the OnClick event messages resume (until the next stamp). Thanks for taking time to look at this - I do appreciate it. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28264> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28264] Turtle.onclick events blocked by Turtle.stamp
George Fagin added the comment: When you say "left click always moves the turtle" I fear my explanation was not clear enough. A left click always moves the turtle in my version as well. What changes when stamp is activated is that OnClick events are not issued when you click on the turtle. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28264> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28264] Python 3.4.4 Turtle library - Turtle.onclick events blocked by Turtle.stamp
New submission from George Fagin: After a Turtle.stamp() command, turtle click notifications enabled via Turtle.onclick() are blocked until subsequent turtle commands are issued. Examples of the functions that re-enable click notifications include undo(), fd(0), left(0), etc. I've verified this behavior on both Python 3.4.2 (my Raspberry Pi) and Python 3.4.4 (my Windows 7 laptop). The attached sample code demonstrates that it's not difficult to work around the issue by using one of those functions immediately after any Turtle.click(), but I'd think that should be handled by the library to it's transparent to the user. -- components: Library (Lib) files: click_and_stamp.py messages: 277306 nosy: George Fagin priority: normal severity: normal status: open title: Python 3.4.4 Turtle library - Turtle.onclick events blocked by Turtle.stamp type: behavior versions: Python 3.4 Added file: http://bugs.python.org/file44800/click_and_stamp.py ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28264> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
