[comp.windows.x] Drawable <--> user-defined data

warlock@csuchico.edu (John Kennedy) (03/03/90)

  I'm looking for the "best" way to transfer user-defined data (say an array
of char) and put it into a drawable (color).  The only way I can see now with
the current X11R4 Xlib documentation is to convert the drawable into an XImage
and the get at the data field.  In addition, I have the following situation:

  Running on a Sun 3/60 or SPARC using cgfour and cgsix frame buffers.
  X11R4 (Standard distribution)
  We're looking for *speed* out of this operation

  The operation will be used to copy the contents of the frame buffer memory
into a drawable so the screen can be fully managed by X when we aren't using
speedy frame-buffer functions (for those in the know, the cgfour is too slow to
alter quickly using window-related functions, so a program I wrote directly
accesses frame buffer memory, leaving the screen with incorrect contents as far
as X is concerned).  Basically, I want to take the image on the screen and
store it in the drawable so X has the same image.

  The area X and I are sharing is a 769 by 769 square.


Warlock, AKA              +----------------------------------------------------
John Kennedy              | uucp:     lampoon!warlock@csuchico.edu
CSCI Student	          | internet: warlock@csuchico.edu
CSU Chico                 +----------------------------------------------------
--
Warlock, AKA              +----------------------------------------------------
John Kennedy              | uucp:     lampoon!warlock@csuchico.edu
CSCI Student	          | internet: warlock@csuchico.edu
CSU Chico                 +----------------------------------------------------

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (03/06/90)

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.