freenode/#clim - IRC Chatlog
Search
2:43:39
|3b|
how do i make a backend use simple-event-queue? (or otherwise force it to check events on same thread that created windows)
3:25:05
|3b|
yeah, better with that... now have a single window i can click on that maybe makes other windows pop up
6:15:06
TMA
jackdaniel: microsoft windows do the "most of the window" trick |3b| mentioned. moreover they do not render for each dpi, the other part of the window is interpolated
9:55:50
scymtym
many of our applications have a NEW-PROCESS keyword parameter in their entry point function. should the new thread use the same server-path/port configuration as the calling thread?
10:01:13
jackdaniel
they use defaults right now. but it is not a standard keyword. I don't think it will be controversial to add *default-server-path* to the thread initial bindings
10:02:16
jackdaniel
n.b: i.e in hierarchy-tool test I'm rebinding default-server-path for tests, I think that drawing-tests do the same for new windows
10:09:48
jackdaniel
if anyone feels like reviewing further drag-and-drop fixes here goes: https://github.com/McCLIM/McCLIM/pull/820
10:11:40
jackdaniel
I've decided on a separate function for the destination defined with a :destination-translator keyword
13:03:39
scymtym
jackdaniel: could you verify something for me? if you (clouseau:inspect (make-list 1000)), then click-and-drag where is says "0 ... 30 shown", is only the interactor pane but not the inspector pane responding to pointer-motion?
13:11:17
jackdaniel
if you add :multiple-window t to the tracking-pointer it should "catch" all panes
13:12:23
jackdaniel
so you could either bind stream to (find-pane-named frame 'inspector) instead of *standard-output* or use multiple-window variant (probably the former suits you more)
13:15:46
scymtym
but wouldn't it be better to use the correct sheet, i.e. the one containing the presentation, in TRACKING-POINTER?
13:17:57
jackdaniel
your call to tracking pointer "doesn't know" anything about the command it is invoked in, so it can't tell where was the object clicked
13:18:43
scymtym
yes, for the other version, i made a presentation-to-command-translator, that looked up the presentation's sheet and passed it to the command
13:21:10
jackdaniel
there could be downsides, if the action is limited only to the sheet, then you don't want possibly trigger same action on another sheet
13:21:37
jackdaniel
scymtym: how about (clim:pointer-sheet (clim:port-pointer (port *standard-output*))) ;?
13:23:02
scymtym
for the clouseau thing, i would just use a scrollbar, but that doesn't work at the moment, right?
13:25:20
scymtym
the BOX-ADJUSTER-GADGET problem may be more complicated. could it require pointer grabbing?
13:29:34
jackdaniel
which use is implied by either: dragging-output, drag-output-record and frame-drag-and-drop (aka presentation dnd translators)
13:31:49
scymtym
i use grabbing in the wider sense here, i.e. also meaning delivering events to a sheet other than the one under the pointer