I agree, Zentara with pretty much everything you said. I didn't realize, until one of your recent posts that the memory leak with Listbox didn't occur when you pass an array reference to the Listbox and manipulating its contents through that. I'm going to take a look at setting up MListbox to use that. Unfortunately, if I do, then it won't be backwards compatible, since it will rely on an API change in 804*.
It's barely worth mentioning, but your solution using HList will still leak if you end up getting smaller result sets, and you are forced to delete entries. The point is, the leak will be significantly less than if you were deleting and recreating everything each update. Reconfiguring is also more efficient for updates than deleting/recreating everything.
RobIn reply to Re^2: perl/Tk and expandable widgets
by rcseege
in thread perl/Tk and expandable widgets
by Elijah
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |