Tk Source Code

View Ticket
Login
Ticket UUID: d6a1bc30cdce08d9682e79e790d987acec491d8d
Title: Order of bindings in man bind doesn't reflect the default bindtags
Type: RFE Version: 8.6
Submitter: mjanssen Created on: 2021-11-11 23:09:49
Subsystem: 01. Bindings Assigned To: fvogel
Priority: 5 Medium Severity: Minor
Status: Closed Last Modified: 2021-11-12 14:42:12
Resolution: Fixed Closed By: fvogel
    Closed on: 2021-11-12 14:42:12
Description:
The default bindtag order for any Tk widget is:

1) widget
2) widget class
3) toplevel
4) all

In the introduction of manual page for [bind] the order of toplevel and widget class is reversed which could imply that the toplevel bindings are regarded before the widget class.

For consistency the order of the two items should be swapped.
User Comments: fvogel added on 2021-11-12 14:42:12:
Merged into core-8-6-branch and trunk.

mjanssen added on 2021-11-12 14:07:23:
Yep, that is what I meant. It was really nitpicking but thanks for the fix.

fvogel added on 2021-11-12 12:34:11:

This was like this in the man page since the beginning of time. I don't see the order as a real problem since the four bullets describe four different matching cases. The order is not really important I think since it is given by the bindtags command. That said, we can change the order (for that same reason), see [b4528784db]. Is this what you suggested?