I see six places invoking this command. We cannot use
[<widget> invoke] as that bypasses even processing. The
only way I see to get around using internal is to use
[event generate] to explicitly simulate a mouse click.
Which is a bit ironic because "tkButtonInvoke" was written
exactly to simulate a click on the button with the mouse
when the button is invoked through the keyboard. It is
exactly this for which the command is used here in the
example, but we are not allowed to do so as it is declared
private.
Question: Do we have plans to make parts of the ::tk
command public ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
workaround
Logged In: YES
user_id=80530
Committed workaround. Leaving bug open, because the
real fix is to stop accessing Tk internals.
Logged In: YES
user_id=75003
I see six places invoking this command. We cannot use
[<widget> invoke] as that bypasses even processing. The
only way I see to get around using internal is to use
[event generate] to explicitly simulate a mouse click.
Which is a bit ironic because "tkButtonInvoke" was written
exactly to simulate a click on the button with the mouse
when the button is invoked through the keyboard. It is
exactly this for which the command is used here in the
example, but we are not allowed to do so as it is declared
private.
Question: Do we have plans to make parts of the ::tk
command public ?
Logged In: YES
user_id=80530
increased priority. as 8.4 release approaches this is more
important.
status?