Xref: utzoo comp.windows.x.motif:2691 comp.windows.x:35753
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!mips!apple!fernwood!uupsi!sunic!ugle.unit.no!pat.tih.no!alpha.tih.no!karlm
From: karlm@alpha.tih.no (Karl Martin Lund)
Newsgroups: comp.windows.x.motif,comp.windows.x
Subject: Re: Way to get list of form's children?
Keywords: form, Motif
Message-ID: <1991Apr25.232311.9908@edb.tih.no>
Date: 25 Apr 91 23:23:11 GMT
References: <550@shrike.AUSTIN.LOCKHEED.COM>
Sender: newsadm@edb.tih.no (News - Olet)
Distribution: comp
Organization: Trondheim College of Engineering
Lines: 24
Nntp-Posting-Host: alpha.tih.no

In article <550@shrike.AUSTIN.LOCKHEED.COM>, behner@AUSTIN.LOCKHEED.COM (Ralph Behner) writes:
|> In Motif 1.0, I am creating a form and then creating children of the
|> form.  Is there a way to later find out what the form's children are,
|> besides keeping track of them as created?
|>                                  Thanx in advance for any help,
|>                                   Max B.
|> 
|> -- 
|>  Max Behner                        | "I used to be disgusted - now I 
|>  Inter: behner@austin.lockheed.com |  try to be amused!"
|>  UUCP:  ut-emx!lad-shrike!behner   |                    (Elvis lives)
|>  Phone: (512) 386-2556             |                                 



I'm sorry I can't help you; i've got the same problem myself. But i would like a way to get access to any widget's children.

My problem is that i have a bulletin board dialog that contains two edit fields, three pushbuttons and some lables. When the user presses the OK-button a callback function is called. Then I would like to have access to the text in the edit fields, but those widgets are defined in a different function. Do I have to define all widgets globally, or is there a simpler and cleaner way. I know about sending arguments to the callback routine, but what about the second (and third and.... widget).

Help on this matter would be highly apprechiated (where is my diksjonary??? :-)


KMLUND. (This would not be a problem on an Amiga...)
(Perhaps it's no problem here either??)