On Mon, May 4, 2009 at 12:15 AM, Darin Fisher da...@chromium.org wrote:
Painting is not the only issue. On Windows there are several ways in which
the thread responsible for a HWND can block waiting for the thread
responsible for a child HWND to respond. Are you sure there are no X calls
The only thing I can thing of that involves a
client-server-client-server-client world tour in X is selection
handling, but that's asynchronous. Querying window properties only
looks at server state (also true for the Mac's window server--there's
no such thing as a synchronous call from the
On Mon, May 4, 2009 at 1:08 AM, Dean McNamee de...@chromium.org wrote:
On Mon, May 4, 2009 at 12:15 AM, Darin Fisher da...@chromium.org wrote:
Painting is not the only issue. On Windows there are several ways in
which
the thread responsible for a HWND can block waiting for the thread
On Mon, May 4, 2009 at 5:48 PM, Darin Fisher da...@chromium.org wrote:
On Mon, May 4, 2009 at 1:08 AM, Dean McNamee de...@chromium.org wrote:
On Mon, May 4, 2009 at 12:15 AM, Darin Fisher da...@chromium.org wrote:
Painting is not the only issue. On Windows there are several ways in
which
On Mon, May 4, 2009 at 9:01 AM, Dean McNamee de...@chromium.org wrote:
On Mon, May 4, 2009 at 5:48 PM, Darin Fisher da...@chromium.org wrote:
On Mon, May 4, 2009 at 1:08 AM, Dean McNamee de...@chromium.org wrote:
On Mon, May 4, 2009 at 12:15 AM, Darin Fisher da...@chromium.org
wrote:
Painting is not the only issue. On Windows there are several ways in which
the thread responsible for a HWND can block waiting for the thread
responsible for a child HWND to respond. Are you sure there are no X calls
that block in a similar fashion? Are there no cases where you can query
