Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!haven!decuac!shlump.nac.dec.com!riscy.dec.com!fuel.dec.com!graham
From: graham@fuel.dec.com (kris graham)
Newsgroups: comp.windows.x
Subject: Re: Dec Toolkit PIXMAP/Label question
Message-ID: <1462@riscy.dec.com>
Date: 1 Sep 89 01:52:13 GMT
References: <226@xpiinc.UU.NET> <5840022@wdl1.UUCP> <1459@riscy.dec.com>
Sender: news@riscy.dec.com
Lines: 71


In article <226@xpiinc.UU.NET>, ctr@xpiinc.UU.NET (Christian Reimer) writes:

> Subject: Re: Dec Toolkit PIXMAP/Label question
> Date: 31 Aug 89 16:16:01 GMT
> 
> In article <1459@riscy.dec.com> graham@fuel.dec.com (kris graham) writes:

>The following is a sample of how to create pixmaps with the DECwindows toolkit.
>
>static Pixmap MakePixmap(dpy, root, data, width, height)
>    Display     *dpy;
>    Drawable    root;
>    short       *data;
>    Dimension   width, height;
>{
>    Pixmap pid;
>    unsigned long       ScreenNumber;
>    ScreenNumber = XDefaultScreen (dpy);
>    pid = XCreatePixmapFromBitmapData (dpy, root, data,
>                (Dimension) width, (Dimension) height,
>                (unsigned long) BlackPixel (dpy, ScreenNumber),
>                (unsigned long) WhitePixel (dpy, ScreenNumber),
>                (unsigned int) DefaultDepth (dpy, ScreenNumber));
>   return(pid);
>}

>>I don't see any DECwindows toolkit calls here, do you?

You are missing the point.   Arguing about not seeing  "any DECwindows toolkit calls "
does not solve the base problem.   What causes the program to bomb was due to
an oversight in the use of an Xlib routine.   I  communicated with the base article's
author off-line..and his problem is solved.
It's common practice to ( be able to ) mix and match Xlib routines with most toolkits...be it 
from HP, DEC, Sun, or "St. Elsewhere" ;-)

>Using the term "DECwindows" gives the impression that you are talking
>about some proprietary DEC system, not the freely distributed X Window System.

This is unnecessary harassment....
I guess the name DEC in anything makes a product "PROPRIETARY"....heh ?  ;-)
Maybe it should  have been called OPENXXXXX......

DECwindows is  an epitome of an architecture that DIGITAL assigns to designs (products)
that imbibes the X philosophy.   (Sorry to those offended by any  "marketeering" in this
definition).

>There ARE people out there that do not automatically make the identification
>between DECwindows and X.  Let's not confuse them further by abusing our
>terminology.

If this is true, then it rather unfortunate.  There is enuff literature out there to
help resolve this confusion.    MIT's implementation of X  should be seen more
like specs, and how-it-should-be-done....rather than branding it the de facto
everything (adherence to the specs is the most important thing).  Most of
the programs on the X tape are contributions that show how things should
be done...the X-way.....that is.

>By the way,
>Does anyone have an example which *really* shows how to use the DEC toolkit
>to do  something simple (like make a label widget with a pixmap label) without
>having to pull one's hair out?

I pray that you do not get "bald" as a result of using  "the DEC toolkit  to do  something 
simple " ;^)

-- 
Christopher Graham          "Discontent is the first step in the progress of humans, beasts,
Digital Equipment Corp       and nations"           
Ultrix Resource Center                                            
New York City        (representing free speech...not DIGITAL)