14:42:02beachTypically in another language, you create a button and you pass a function to the button creator, and that function gets called when the button is pressed.
14:42:29beachIn Common Lisp, that's nothing special but in languages like C it is actually very complicated because they don't have closures.
14:43:19beachIn Common Lisp, the button-press code often calls some generic function instead. Client code puts a method on that generic function to handle the push. So the method plays the same role as a callback, but the mechanism is different.
14:45:32lokejackdaniel: I have a test case now, that refuses to display a font.
14:56:26fittestbitsHmm. When I first started porting mcclim to mezzano, I had to add a font directory to the list of places mcclim searchs for fonts. Wonder what's different ...
15:10:32nyefOn the subject of callbacks, there's another way to look at it: In most languages, callbacks are a function /and a pointer for callback-specific data/, because they don't have closures.
15:13:31nyefHunh. And CLIM II 30.3 explicitly calls out application frames as being event clients. I wonder if there are earlier references to this concept?
15:20:18lokeOK, now I've tested on Arch Linux, Fedora-26 and Debian-9. All fo them fails in the same way.
22:21:24oleo'(3 + 2); evals to 5 as well as (3+2)$ etc
23:04:20scymtymjackdaniel: i have found a promising way of investigating flickering in mcclim (clx backend): in sbcl, (trace xlib::buffer-flush :print-after (sleep .05)). then try something like highlighting and unhighlighting a presentation in the bordered-output demo