On Thursday, July 2, 2015 at 5:34:19 PM UTC-5, Ben Elam wrote:
> I've stripped things down to the least amount of code necessary to reproduce
> the error. I can make tk.Button handle event '<3>' but not event '<1>'. That
> is, the function the event is passed to receives the event and can even pr
On Thursday, July 2, 2015 at 6:42:22 PM UTC-5, MRAB wrote:
> On 2015-07-02 23:33, Ben Elam wrote:
> > I've stripped things down to the least amount of code necessary to
> > reproduce the error. I can make tk.Button handle event '<3>' but not event
> > '<1>'. That is, the function the event is pas
On Thursday, July 2, 2015 at 5:54:50 PM UTC-5, Terry Reedy wrote:
> On 7/2/2015 6:33 PM, Ben Elam wrote:
> > I've stripped things down to the least amount of code necessary to
> > reproduce the error. I can make tk.Button handle event '<3>' but not
> > event '<1>'. That is, the function the event i
On 2015-07-02 23:33, Ben Elam wrote:
I've stripped things down to the least amount of code necessary to reproduce the error. I can
make tk.Button handle event '<3>' but not event '<1>'. That is, the function the
event is passed to receives the event and can even print the address of the event o
On 7/2/2015 6:33 PM, Ben Elam wrote:
I've stripped things down to the least amount of code necessary to
reproduce the error. I can make tk.Button handle event '<3>' but not
event '<1>'. That is, the function the event is passed to receives
the event and can even print the address of the event obj
I've stripped things down to the least amount of code necessary to reproduce
the error. I can make tk.Button handle event '<3>' but not event '<1>'. That
is, the function the event is passed to receives the event and can even print
the address of the event object, but a callback later produces a
