Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!tut.cis.ohio-state.edu!ucbvax!earth.cchem.berkeley.edu!garys
From: garys@earth.cchem.berkeley.edu (Gary Shea)
Newsgroups: comp.windows.x
Subject: Change in Xaw Form widget
Keywords: Xt Xaw Form Widget
Message-ID: <33518@ucbvax.BERKELEY.EDU>
Date: 7 Jan 90 22:47:16 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: garys@earth.cchem.berkeley.edu (Gary Shea)
Distribution: usa
Organization: U.C. Berkeley Dep't of Chemistry
Lines: 25

A note of caution for XToolkit/Athena widget programmers.

If you have subclassed the Form widget (ripped off the Dialog
widget for your own evil purposes perhaps, as I did :), be aware
that the "empty" field of the FormClassPart is now being used.
I found it necessary to mimic the initialization in Dialog.c
in order to stop those distracting segmentation violations.
(Sun 3/50, 4.0.3, mono)

Ideally, inocuous changes of this sort could be
hidden by use of the *ClassPart structure definition everywhere,
but unfortunately the initializer for the subclass must explicitly
initialize the entire *ClassRec, so there seems to be
no way to hide the change completely.  I don't think there
is any notion of class initializers at the moment
(at least in Xaw), might that be a possible solution to
the problem?

Last and hardly least, a word of thanks to the MIT folks
and all the rest of you who have contributed to X11r4.
Very impressive.

Gary Shea
garys@earth.cchem.berkeley.edu
shea@csvax.cs.ukans.edu