freenode/#clim - IRC Chatlog
Search
4:14:22
nyef
Should TRACKING-POINTER take an X11 mouse grab? Does it in original-CLIM or McCLIM? If it does not / should not, is there some way to take such a grab? What about a keyboard grab?
4:29:15
nyef
(Yes, I would want a keyboard grab that can override the usual window-manager Meta-Tab hook.)
13:24:59
slyrus
OK. 12.5.1 draw-text is rather confusing, to me. we have toward-x and toward-y and we have transform-glyphs.
13:26:41
slyrus
I think this means that one can use toward-x and toward-y, relative to x and y, to figure out the angle of the baseline for the text
13:27:50
slyrus
but how should the text be drawn relative to this baseline? default to use the angle of the baseline so that we end up with rotated text or default to angle 0 so that the individual letters are straight up and down?
13:29:00
slyrus
if transform-glyphs is true then we rotate each glyph by the amount spec'ed in the rotation transformation, but relative to what starting value?
13:29:29
beach
Let me read it. I think CLIM assumes that text can not be rotated. Or at least, allows for implementations to have this limitation.
13:32:06
jackdaniel
we are not using x11 glyphs by default but draw things and pass them with render extension
13:33:22
slyrus
that's what I thought. so even the non-render X11 backend requires render. great. :)
13:34:12
jackdaniel
well, render backend in principle was designed to work with arbitrary framebuffer-enabled toolkit
13:36:33
beach
slyrus: The description of draw-text looks clear to me. If toward-x and toward-y define a non-trivial angle and transform-glyphs is true, then the entire text should be rotated so that it looks "normal".
13:36:34
jackdaniel
sorry, I'm a bit busy now, just chipped in to say that we don't use x11 core fonts
13:37:33
jackdaniel
slyrus: render which is "interactive" - ie not only draws, piggybacks on clx, and that's what clx-fb is all aobut
13:38:16
jackdaniel
I don't know the details (didn't read much into Alessandro code - he wrote this backend)
13:38:39
beach
slyrus: Then the glyphs are aligned with the axes as usual, but presumably the left baseline point of each one is on the line defined by toward-x and toward-y.
13:39:28
slyrus
so in the case where render-glyphs is true, what is the impact of the specified rotation transformation?
13:41:41
beach
I mean, transform toward-x and toward-y through the rotation transformation. then transform the glyphs according to the result.
13:44:07
slyrus
hmm... maybe I'm just dense but it's still not clear to me what the effect of the current transformation should be.
13:45:17
beach
So, the starting position together with toward-x and toward-y define a vector. If you take that vector and transform it through the transformation, you get a new vector. That new vector defines an angle.
13:48:05
slyrus
also, the implication of implementations ignoring transform-glyphs can be 1) text is always aligned on the toward-{x,y} vector or text is always aligned to the x-axis.