Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!think!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: Drawable <--> user-defined data
Message-ID: <9003061401.AA03728@expire.lcs.mit.edu>
Date: 6 Mar 90 14:01:16 GMT
References: <1990Mar02.220228.24964@csuchico.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 21

I'm probably just not awake yet, but I found your message very confusing.

    for those in the know, the cgfour is too slow to
    alter quickly using window-related functions,

I'm in the know, and I don't know that. :-)  That's rather a blanket
statement, more particulars to back up the statement would be nice.
I can't even tell if you're talking about graphics functions or
window tree manipulation functions, or what.

    so a program I wrote directly accesses frame buffer memory, leaving the
    screen with incorrect contents as far as X is concerned

If you're just manipulating the "insides" of a window (i.e. the graphic
content), then the server doesn't really care what you've done.

    Basically, I want to take the image on the screen and
    store it in the drawable so X has the same image.

Perhaps you don't understand, what's on the screen *is* all that "X has"
(unless backing-store/save-unders are involved) for window contents.