freenode/#clim - IRC Chatlog
Search
16:34:05
frgo
Hey, it's me again. Sorry for reaching out again with my "Attempt to use closed display" issue. I found the following: See https://gist.github.com/dg1sbg/e264f4e5ce7293f6b76d77e4e6a9bd6f
16:36:02
frgo
I then let stuff just sit there and, after some minutes of not doing anything, this error showed up.
16:48:25
ck_
so, something is closing your display, maybe it's a good idea to trace close-display and find out what
17:29:41
Inline
i have to quit the repl and restart, otherwise it doesn't matter if i even do a setf on my display
17:32:46
frgo
Yep - that's exactly my problem. I somehow need to make sure that I don't run into a timeout of some sort.
17:33:56
Inline
so i run a clx program, the display got closed, i setfed the display anew to a new instance and checked that it is alive (:dead nil), and reran the program, but the program just returned closed-display error
18:08:08
frgo
Question to the CLX gurus here: In 'buffer-input (in file buffer.lisp in sharplisper's CLX), when a timeout occurs, the buffer is closed. I do not understand this - if is not an error, just a timeout ...
18:24:38
jackdaniel
frgo: try replacing allegro-specific buffer-input-wait-default with the one in dependent.lisp
18:25:41
jackdaniel
as of why buffer is closed on timeout, I can only guess that it is by design: if X fails to respond in timely manner it is considered dead
19:06:11
ck_
We'll see where this goes. Through the power of detachment, I can just sit back and watch
19:08:12
jackdaniel
so I wouldn't be bothered much. that said we may indeed work on code on our side to call this function less if it is uncommon in x11 protocol `standards'
19:08:28
ck_
I believe his point is that the caching already happens, and that querying the depth so often is a mistake
19:14:34
ck_
I had a very quick look at the macro (attributes.lisp+309), but couldn't see where the depth is cached in those related functions