Jitterbug-Id: 28
Submitted-By: guido@python.org
Date: Wed, 14 Jul 1999 14:00:14 -0400 (EDT)
Version: 1.5.2b
OS: 


Mark Lutz wrote me:

(BTW, this will probably never surface again (I'm stressing
the image object a bit), but I think there's a problem
with using the id() of an image as its name.  I ran into
a situation where an image was drawn in the wrong place, 
because a newly allocated image object had the same id()
as one very recently reclaimed.  It's very obscure, will
only happen if you have > 1 canvas in a process and happen
to be creating and deleting images very quickly, and is
too complex for me to describe further at the moment ;-).
I worked around it by first generating image names from a
simple counter, and then prebuilding all images up front.)



====================================================================
Audit trail:
Wed Jul 14 14:00:28 1999	guido	moved from incoming to open

Fixed in patch 101424, http://sourceforge.net/patch/?func=detailpatch&patch_id=101424&group_id=5470

Should be fixed by Martin's patch (#101424).  I've accepted the patch and assigned it and this bug to Martin for checkin and closure.