freenode/#clim - IRC Chatlog
Search
7:46:00
jackdaniel
if I understand correctly you've suggested that xcb is thread-safe. but it speaks x11 protocol with arbitrary peers connected to the same server. I'm confused
7:46:20
jackdaniel
if x11 protocol can't be used in a thread-safe manner, then xcb could not achieve such feat
7:49:59
jackdaniel
so if <---> can't be implemented so asynchronous access works OK, then no x11 client could be thread-safe by definition
7:50:39
jackdaniel
and if x11 client sends something else than what x11 server expects, then you have garbage in, and depending on the server you have either garbage out or proper errors about invalid requests
7:51:32
jackdaniel
so xcb could only lift mitigations which were imposed by xlib architecture, but clx does not inherit architecture of xlib (despite the package name)
8:07:00
PuercoPope
I stand corrected, the problem was not at the protocol level but with the xlib implementation. rfc1013 mentions the unique ids per request.
9:02:37
loke
DISPLAY-BOFFSET is an accessor to the DISPLAY structure, and INDEX+ just adds index values.
14:02:59
scymtym
jackdaniel: i'm pretty sure i figured out the remaining issues with our event processing
18:22:17
jackdaniel
scymtym: sorry, I didn't get to the pull request today. I will look into it as a first thing tomorrow.
18:36:29
jackdaniel
question: should we specify that polygons and bezier ares are assumed to be not self-intersecting or do we want to have medium-draw-* implement either non-zero or even-odd rule? or shall we make that a parameter?
18:44:05
jackdaniel
and by properly do you mean a non-zero fill rule or a parameter allowing specification of the rule?
18:45:39
ck_
parametrization would be the most right thing if I think about it. But this could benefit from looking at some use cases, and I can't think of one at the moment
18:46:40
jackdaniel
adding a parameter would change the api, so deciding on one rule (or saying that they must be "simple") is more practical