freenode/#clim - IRC Chatlog
Search
4:49:40
ck_
loke: I have very limited, but some experience with drei and its test suite, would you like a second pair of eyes?
6:28:50
loke
ck_: well, my problem is that after some chage in the last few months, my custom DREI bindings no longer works.
6:30:13
loke
In short, the input loop of Climaxima is currently completely broken, because of DREI beingind no longer working and changes that prevents my Shift-Return check from working. JD told me the latter was fixed, but I need to make changes to the code to make it happen, changes that I have been unable to get to work.
6:32:01
loke
I shouldn't complain too much right now since I haven't been very precent in the last few months. This would have been much easier to deal with if I had found the incompatibility at the time when these changes were pushed to master, rather than several months later.
6:35:16
loke
ck_: I really could use some help with this one, and if you're willing to assist you could build climaxima and test for yourself?
6:42:47
jackdaniel
afair climaxima is very liberal with accessing internal symbols and assuming things that are not guaranteed by CLIM, maybe there's the issue?
6:44:22
loke
I'm guessing it's something simple that is hidden by the fact that the "return" stuff isn't working... Hmm... now that I think about it... Maybe it's as simple as the history not being updated, and M-p actually works, but there is simply nothing to show?
6:45:56
loke
jackdaniel: Thank you. That seems to be the problem. That means that the Drei issue was a red herring. The problem happened before.
6:46:53
loke
jackdaniel: You told me that the you fixed the problem with Shift-Return was fixed. How was it fixed? Clearly my workaround which accessed internal symbols can't be used anymore. WHat is the proper way to do it?
6:49:30
loke
So you're saying that the flags are available in the gesture itself now, rather than me having to look at the previous event?
6:58:52
loke
jackdaniel: Looking into it now. For me, STREAM-READ-GESTURE doesn't return when I press shift-return. For some reason that action is dropped somewhere. Note that I'm using the drei-input-editing thing, so perhaps the gesture is dropped there somewhere. Checking now.
7:58:52
loke
From the toplevel I see a call to STREAM-READ-GESTURE that doesn't return when I press Shift-Return, but I can see a lot of processing happening when I do. I just wonder where in earth this gesture is dropped so as to not be returned.
8:01:22
jackdaniel
that's another example of why I think that drei is not very composable with the rest of clim
8:25:29
ck_
you mark fdefinitions by calling slime-trace-dialog-toggle-trace, then run the thing you want to look at; afterwards, you open slime-trace-dialog and from there you can follow the notes on the screen
8:37:53
loke
jackdaniel: I think I found it... PROCESS-GESTURES throws an error UNBOUND-GESTURE-SEQUENCE when you hold shift and press return.
9:25:37
ck_
Well it could mean that either the gesture gets mangled, or the command-table doesn't contain it, no?
9:26:38
jackdaniel
I don't think that it is part of clim specification, so it is another internal esa protocol -- in this sense finding that this condition is signalled doesn't say much about a nature of the problem
9:29:24
ck_
I tried reading through the spec to understand things better, but couldn't go on because of semantic satiation -- 'gesture' has lost all meaning to me
9:31:17
ck_
process-gestures mentions this condition explicitly in its docstring. No matter if it is part of the specification or not, would you agree that the two reasons I have listed warrant examination now? (or do you think the reason is elsewhere)
9:32:00
jackdaniel
ck_: gesture is an abstracted "user interaction" (i.e select, edit, etc), triggered i.e by a mouse click or keyboard press (possibly, but not yet in McCLIM, touch gesture)
9:32:52
jackdaniel
I'm not saying that it is not a clue or worth examining, I'm saying that the information presented does not constitue "found IT"
9:42:00
ck_
loke: is there a way for me to get this behaviour without building all of climaxima and its requirements?
9:44:39
ck_
or, as a separate question, have you tried redefining add-maxima-input-editor-command analogous to jackdaniels example in a10aad6b-xxx.lisp ?