Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!mintaka!bloom-beacon!EXPO.LCS.MIT.EDU!kit
From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson)
Newsgroups: comp.windows.x
Subject: Re: Widget Client data (info request)
Message-ID: <9002212125.AA01934@expo.lcs.mit.edu>
Date: 21 Feb 90 21:25:00 GMT
References: <1990Feb21.180509.21801@agate.berkeley.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 35


>> me
> Setve
me

>>There is no way to do this directly.  You can, however, use the X Context
>>Manager to associated data with a widget id.  Kind of a hack, but it will work.
>>
>>See Gettys, Scheifler and Newman section 10.12.
>>

>Wait a second - we're talking about "client" data; not "server" data!

What has the server got to do with this?  The X Context manager is handled
entirely on the client side.

>This is a little bit more than "kind of a hack" :-). Clearly, client data
>belongs in the client, and not in the server. It probably wouldn't work,
>anyway, since programmers may wish to associate client data with unrealized
>widgets that don't have windows yet.

True, of you do exactly what the manual says and use the window you will
not be able to use this with unrealized widgets, but the "window" the context
manager needs is really just a unique id that is the size of a window id.  since
both window id's and widget id's are unique and the same length...

Like I said it is "kind of a hack".  But there is no server interaction here at
all.

						Chris D. Peterson     
						MIT X Consortium 

Net:	 kit@expo.lcs.mit.edu
Phone:   (617) 253 - 9608	
Address: MIT - Room NE43-213