9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ralph Corderoy <ralph@inputplus.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm and FreeBSD
Date: Fri, 21 Mar 2003 09:59:41 +0000	[thread overview]
Message-ID: <5ad6.3e7a4899.14367@blake.inputplus.co.uk> (raw)
In-Reply-To: <3E7771FC.33FE8147@null.net>

Hi,

> BRL's involvement in the X11 part would be mainly Gary Moss and to a
> lesser extent myself.  The only use of XCopyArea in our version of
> sam/xterm is the bitblt() function, and there are no special
> precautions or comments there.  XFillRectangle is used in three
> places, rectf() (same notes as for bitblt()) and texture(), where
> color depth 1 is handled somewhat differently due to X-server not
> supporting it.  But there doesn't seem to be anything about order of
> the actions.

Stuff like XCopyArea or XCopyPlane is often found to exhibit bugs when
an accelerated server backend has replaced the standard `device
independent' implementation.  Has anyone snooped the protocol when it
fails and sent off the relevant snippet to the server maintainers?  It
seems unlikely the client could be doing anything wrong.

> There does exist an XSynchronize() function that could
> be inserted into the problematic application to help enforce
> sequencing, which might at least help you to identify the exact
> problem.

If drawterm is an Xt Intrinsics application then -synchronous on the
command line would have the same effect.

Cheers,

-- 
Ralph Corderoy.      http://inputplus.co.uk/ralph/     http://troff.org/


  reply	other threads:[~2003-03-21  9:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 16:33 Philippe Anel
2003-03-13 22:19 ` Russ Cox
2003-03-13 23:20 ` Russ Cox
2003-03-17 11:43 ` Boyd Roberts
2003-03-19 10:03   ` Douglas A. Gwyn
2003-03-21  9:59     ` Ralph Corderoy [this message]
2003-03-21 11:24       ` Philippe Anel
2003-03-21 18:49         ` Russ Cox
2003-03-21 19:44         ` Russ Cox
2003-03-24 10:12           ` Ralph Corderoy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5ad6.3e7a4899.14367@blake.inputplus.co.uk \
    --to=ralph@inputplus.co.uk \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).