Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!cvl!ai.etl.army.mil!anneb
From: anneb@ai.etl.army.mil (Anne Brink)
Newsgroups: comp.windows.x
Subject: XCopyArea woes (summary)
Keywords: XSync(), hardware, homegrown
Message-ID: <403@ai.etl.army.mil>
Date: 21 Feb 90 22:01:04 GMT
Distribution: na
Organization: USAETL, Fort Belvoir, Virginia
Lines: 31


Hi again, everyone!

Last week, I posted asking for help with a problem that I was having with
XCopyArea(). 1) it's too slow,  and 2) it hogs the server.  I recieved a
few responses, and here's what's what:

The simple problem of the mouse clicks not registering was solved by adding
an XSync() call... I am embarrased to admit that I didn't put one in in the
first place, and more embarassed that I didn't notice this when the problem
manifested itself.  Insert red face here.  Oh, well, when I get to be a
notorious X programmer, these things will cease to escape me.

As for the speed that the program runs at _after_ I added the XSync() call, I
received one suggestion to buy a hardware accellerator, which should speed
XCopyArea() (among other things) up noticeably.

Barring that, I'll have to roll my own copy routine.

It seems (by the mail I received on this) that there were one or two posted
replies to my question, which unfortunately didn't make it through. If
you posted a reply to the net, and you saved it, could you be so kind as
to send me a copy?  I'd really appreciate it. 

Anyway, thanks for your help.

				-Anne Brink
-- 
#################################||############################################
  Anne Brink: anneb@etl.army.mil ||    Open Spring Training!!
    ...!uunet!etl.army.mil!anneb || 	  Orioles in '90
#################################||############################################