Using the crude tool of top(1), I learned that viewing the source of a 500K file meant losing 500K down the drain. - If I give the text to the TextDisplay's initial buffer, it knows that it owns it. - Window::destroy() doesn't delete. The header comment in fltk/src/Window.cxx says it's some sort of 'hide' function: "Hides the window and also deletes all window system information about the window, and thus returns it back to the state it was in before the first show(). It is harmless to call this if the window is already destroyed." - And while I was in there, I threw in some callback(window_close_cb, ...)s for closing windows using the window mgr instead of a button.
On Sat, May 03, 2008 at 04:39:34AM +0000, corvid wrote:
Using the crude tool of top(1), I learned that viewing the source of a 500K file meant losing 500K down the drain.
- If I give the text to the TextDisplay's initial buffer, it knows that it owns it.
- Window::destroy() doesn't delete. The header comment in fltk/src/Window.cxx says it's some sort of 'hide' function:
"Hides the window and also deletes all window system information about the window, and thus returns it back to the state it was in before the first show(). It is harmless to call this if the window is already destroyed."
- And while I was in there, I threw in some callback(window_close_cb, ...)s for closing windows using the window mgr instead of a button.
Committed! Funny how the Escape key started working again as close shortcut. -- Cheers Jorge.-
participants (2)
-
corvid＠lavabit.com -
jcid＠dillo.org