Author terry.reedy
Recipients Frank Pae, louielu, serhiy.storchaka, terry.reedy
Date 2017-04-30.18:59:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493578744.82.0.402288093063.issue30200@psf.upfronthosting.co.za>
In-reply-to
Content
Frank, bigger is not better for demonstrating a problem.  The only thing needed for this issue is a tk window with two list boxes.  Having to click twice to get a window with more than just the two Listboxes is just noise.  

Anyway, I downloaded the file as tem.py into a directory on the path and ran "py -x.y -m tem" with the 3 x,y pairs.  For 3.6 I see the traceback Louie Lu posted -- **for 2.7**.

Since clicking in box 2 after clicking in box 1 changes the selection set in *both* boxes, on all 3 versions, there should a <<ListboxSelect>> event for both, on all 3 versions, as specified in the tcl/tk doc that I quoted. I believe it was a bug when the deselect event did not happen.

On Windows, 2.7.13 uses tk 8.5.15, 3.5.z uses tk 8.6.4, and 3.6.z uses tk 8.6.6.  My hypothesis is that the bug of not raising an event for the deselect, at least on Windows, was fixed in tk in 8.6.5/6.  If so, this should be closed as 'not a bug'.

Louie, what tk x.y.z do you have on your linux?

Serhiy, did you change anything in tkinter for 8.6 that could have affected <<ListboxSelect>> events?
History
Date User Action Args
2017-04-30 18:59:04terry.reedysetrecipients: + terry.reedy, serhiy.storchaka, louielu, Frank Pae
2017-04-30 18:59:04terry.reedysetmessageid: <1493578744.82.0.402288093063.issue30200@psf.upfronthosting.co.za>
2017-04-30 18:59:04terry.reedylinkissue30200 messages
2017-04-30 18:59:04terry.reedycreate