Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!sps!arm
From: arm@sps.com (Annette Myjak)
Newsgroups: comp.windows.x.motif
Subject: Re: Toggle Button Woes
Message-ID: <272@sps.com>
Date: 14 Sep 90 14:17:59 GMT
References: <270@sps.com> <142439@sun.Eng.Sun.COM>
Organization: SPS - Indialantic, FL
Lines: 31

In article <142439@sun.Eng.Sun.COM>, argv@turnpike.Eng.Sun.COM (Dan Heller) writes:

> 
> Lastly -- I recognize that I might be mistaken about my analysis
> of your problem.  If you can tell me that you are actually doing:
> 
>     XtAddCallback(widget, XmNvalueChangedCallback, func, 71);
> 
> and the client_data for "func" is indeed 0, then you have a problem :-)
> 
> --
> dan


i verified the data getting passed into the callback before i posted my 
sorrowful tale. i checked the global value just before the XtAddCallback 
statement, and it was set to 71 (in a #define in file included 5 files 
before my included utility file where this callback gets added :-) ).  
just to be sure, i did just what you indicated in the above XtAddCallback
line:  ie, i passed the integer 71.

the callback function says it's getting a 0 for the client_data.

does that mean i really have a problem :-(.

like the original post mentioned, i managed to find a work around, i just
want to know why this doesn't work for this toggle button, but works just
fine for 7 others on another dialog box.

annette
arm@sps.com