Hi,
I noticed some fishy behavior when I started to program with XLib. First, I am running with backing store on and the below problem does not exist with anything but accelerated primitives, so I'm pretty sure that things are not the way they should be. When an accelerated 2d primitive (solid-fill, or copyarea) has all or part of it's destination an area concealed by another window, the concealed area is not altered, no graphicsexpose events are generated by the operation, and no expose events are generated when the area is uncovered. This of course makes it hard for an application that uses such primitives to keep the screen in a sane state. So my question is, 1) Is this a bug, or a misconfiguration on my part? 2) Is the bug known, and if not, how should I create a "ticket" for it? 3) Is there a runtime workaround, like asking the X server not to use accelerated primitives in a certain graphics context? -- Brian _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
