summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1999-05-03 15:38:56 (GMT)
committerGuido van Rossum <guido@python.org>1999-05-03 15:38:56 (GMT)
commit2d6a568a0f6c65c76797556bf949b97ede9049e1 (patch)
treeafd47767aa891897733e89fa1418e8d5aa9e8ae0
parentb46413f274bb53e4a8104adad117f964c0c6ab6d (diff)
downloadcpython-2d6a568a0f6c65c76797556bf949b97ede9049e1.zip
cpython-2d6a568a0f6c65c76797556bf949b97ede9049e1.tar.gz
cpython-2d6a568a0f6c65c76797556bf949b97ede9049e1.tar.bz2
Tim Peters writes:
[W]hile trying to dope out how redirection works, stumbled into two possible glitches. In the first, it doesn't appear to make sense to try to rename a command that's already been destroyed; in the second, the name "previous" doesn't really bring to mind "ignore the previous value" <wink>.
-rw-r--r--Tools/idle/WidgetRedirector.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/Tools/idle/WidgetRedirector.py b/Tools/idle/WidgetRedirector.py
index 45f86f7..b11b0e4 100644
--- a/Tools/idle/WidgetRedirector.py
+++ b/Tools/idle/WidgetRedirector.py
@@ -28,11 +28,11 @@ class WidgetRedirector:
tk = widget.tk
w = widget._w
tk.deletecommand(w)
- tk.call("rename", w, orig)
+ tk.call("rename", orig, w)
def register(self, name, function):
if self.dict.has_key(name):
- previous = function
+ previous = dict[name]
else:
previous = OriginalCommand(self, name)
self.dict[name] = function