freenode/#clim - IRC Chatlog
Search
9:31:47
jackdaniel
previously pressed sheets in X worked as follows: if there is nothing below the pointer what is sensitive to the particular kind of event (i.e pointer motion)
9:32:51
jackdaniel
that works fairly well until you try to scroll with pressed button and you wander above i.e buttons, then scrolling ceases to work
9:33:35
jackdaniel
it is worth noting, that it is not how gtk, firefox and other toolkits behave, so they either order xserver by some means to change this behavior or they do more or less what we do
9:37:45
scymtym
i was wondering how our menus worked before, but yes, X seems to deliver all events to the "pressed" window. i checked with xev which should reflect vanilla X behavior
9:39:22
jackdaniel
given that the leaf menu button was sensitive to events, then these events were not distributed to the pressed sheet but rather to the leaf button sheet
9:40:34
scymtym
for things like scrolling over one sheet after pressing and holding over a different sheet, i'm not sure what the right behavior is
9:43:46
jackdaniel
I think of it as if I were drawing with a pen on a sheet of paper. underlying desk receives pressure as well
9:44:49
jackdaniel
if I were to pick any of these two behaviors (without replication) I'd definetely choose gtk one
9:45:12
scymtym
for gadgets, it often doesn't matter either way since the exit event caused by pointer motion out of the sheet region disarms them
9:48:17
jackdaniel
when you try to scroll things it is enough to navigate above any other sheet to make it stop scrolling
10:19:27
scymtym
by "without replication" i meant only dispatching to the pressed sheet (except for some or all boundary events, maybe)
10:20:13
scymtym
but i can imaging problems with TRACKING-POINTER over multiple sheets and thus drag&drop in general
12:11:19
jackdaniel
we disarm the scroll-bar when release-pointer-event is received, so it clearly should be delivered to the pressed sheet
12:11:59
jackdaniel
then take the case with menu: we want to deliver release-pointer-event to the leaf button, not to the pressed one
12:13:06
jackdaniel
and the gist of the issue is precisely this pointer-release-event. note, that other than that we only replicate pointer motion events
12:24:47
jackdaniel
scymtym: I've pushed to ieh-1 version which delivers pressed-sheet duplicates after the original sheet
12:52:16
jackdaniel
http://asciicker.com/x13/ heh, press #\q or #\e, looks amazing (3d rendered to a console)
14:41:42
scymtym
jackdaniel: i'm convinced that the "clx: do not distribute enter/exit events of kind :INFERIOR" commit is needed for non-leaf panes
19:24:47
jackdaniel
question about test-style-width (http://bauhh.dyndns.org:8000/clim-spec/11-1.html#_585): what is "width of some representative character in the font"?
19:25:42
jackdaniel
as opposed to "it is width property of the character #\M" which is only about glyph width
19:26:32
jackdaniel
my rationale is as following: if we have a fixed-width font I'd expect that if I put rectangles of width text-style-width with alternating colors in a line and then draw a text there
19:28:12
jackdaniel
otherwise it is impossible to draw such grid using clim protocols for fixed font
19:48:52
scymtym
jackdaniel: that commit alone is not enough. i now think that we need to take a step back and actually specify what we want to achieve. i'm writing a draft now
19:59:41
jackdaniel
(if I were writing such document, in a section "goals" I'd put -- get over with these branches, because I have at least 3 more in the oven ;) more seriuosly though, thank you for working on that with me, I'm sure we'll avoid plenty of regressions thanks to your conscientiousness
20:00:17
jackdaniel
good night all o/ I'd appreciate comments on the text-style-width (even if it is only "I agree" ,)
20:04:34
scymtym
i can't wait to get this done as well. i would rather work on double buffering and the other stuff in my queue