Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!ncar!ico!attc!marbru
From: marbru@attc.UUCP (Martin Brunecky)
Newsgroups: comp.windows.x
Subject: Re: Was None now XtSetValues
Message-ID: <944@attc.UUCP>
Date: 18 Dec 90 21:07:36 GMT
References: <9012171804.AA29328@unislc.UUCP> <3235@gazette.bcm.tmc.edu>
Reply-To: marbru@auto-trol.UUCP (Martin Brunecky)
Organization: Auto-trol Technology, Denver
Lines: 25

In article <3235@gazette.bcm.tmc.edu> etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor) writes:
>
>XtSetValues works by first calling the widget's SetValues
>Proc.  If this routine indicates that the widget should
>be redrawn, Xt will issue a ClearArea on the whole widget.
>
   The reason is (likely) to avoid drawing to unmapped
   widgets, and (likely) to avoid timing related race
   conditions, and .....

   But I have (yet another) reason to grief. Some of my widgets
   don't create a window, they create an (off-screen) pixelmap.
   [I see the big WRONG! on your faces]. 
   Such widgets make some things much easier and cleaner, but...
   I cant' allow ClearArea on Pixmap (BadWindow...), so I have
   to use couple nasty tricks to get around it.

   So, while my superclasses "SetValues" can return TRUE, Redisplay!,
   I'd love to have a way of saying: NO, don't do it! in *my* SetValues.
   Unfortunatelly, Xt only or-es responses from all SetValues.
-- 
=*= Opinions presented here are solely of my own and not those of Auto-trol =*=
Martin Brunecky                           {...}sunpeaks!auto-trol!marbru
(303) 252-2499                        (sometimes also:  marbru@auto-trol.COM )
Auto-trol Technology Corp. 12500 North Washington St., Denver, CO 80241-2404