Re^3: Tk::Table clear creates unwanted boxes

choroba, I had tried using delete on the table as well, but that was not working for me. I can not figure out where to use it in my code. If you could demonstrate (especially on my more realistic code), that would be greatly appreciated.

Comment on Re^3: Tk::Table clear creates unwanted boxes Download Code

Replies are listed 'Best First'.
Re^4: Tk::Table clear creates unwanted boxes by Anonymous Monk on Aug 06, 2014 at 00:29 UTC
If you're going to "delete" or destroy, then you should avoid closures :) no closures in Re: Tk::Table cell select/deselect or tk-frame-del-delmejo.pl ... but even though this code (delmejo) doesn't have closures, Tk::Frame does, so destroying frames (like Tk::Table) does leak small memory (Tk.pm implementation issue) Reusing a table (or other widget) with a model/data is probably the best approach if memory is a concert in long-running-program ... see Re: perl tk mainwindow capability (virtual tree widget, huge amounts of data, pageination)	[reply]

Replies are listed 'Best First'.

Re^4: Tk::Table clear creates unwanted boxes
by Anonymous Monk on Aug 06, 2014 at 00:29 UTC

If you're going to "delete" or destroy, then you should avoid closures :) no closures in Re: Tk::Table cell select/deselect or tk-frame-del-delmejo.pl ... but even though this code (delmejo) doesn't have closures, Tk::Frame does, so destroying frames (like Tk::Table) does leak small memory (Tk.pm implementation issue)

Reusing a table (or other widget) with a model/data is probably the best approach if memory is a concert in long-running-program ... see Re: perl tk mainwindow capability (virtual tree widget, huge amounts of data, pageination)

[reply]