freenode/#clim - IRC Chatlog
Search
11:13:04
scymtym
jackdaniel: i came up with a strategy for further investigating the event issues. i made an event logger and visualizer that shows events generated by the port and what gets distributed/synthesized. i it already very helpful, but i need one more thing before i can really attack the actual problem: i have to draw things onto arbitrary sheets. what i have only works for some sheets and is also unreliable. is it even possible to draw onto
11:36:15
jackdaniel
to prevent recording, you may do: (if (output-recording-stream-p sheet) (with-recording-options (sheet :draw t :record nil) #1=(drawing)) #1#)
11:39:21
jackdaniel
in principle we could provide dull method specialized on a sheet invoke-with-output-recording options (which would allow :draw t :record nil and :draw nil :record nil, but not :record t option) but that would be arguably a leaked abstraction
11:40:01
scymtym
jackdaniel: thanks, i did the recording part but for some sheets, nothing appears or something appears quasi-randomly
11:47:29
scymtym
this is the thing: https://github.com/scymtym/McCLIM/tree/stupid-event-logger . (ql:quickload '(:clouseau :clim-examples)), then load event-log.lisp and set *LOGGING* to T and interact with the demo for a short while
11:48:27
scymtym
it should highlight the event sheet and indicate the pointer position if you move the pointer over the event in the inspector
11:53:06
jackdaniel
n.b at one time I've been thinking about a separate "overlay" sheet on which we could draw highlightning or other tips which could span multiple sheets in a frame (something like an overexposed top-level-sheet with transparent background)
11:53:53
jackdaniel
I didn't pursue the idea because of lack of time, but it could be a valuable concept
12:39:41
scymtym
jackdaniel: should a leave event be produced for the parent when entering a child? or is the pointer considered to be "in" both sheets at the same time?