Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph R. Swick)
Newsgroups: comp.windows.x
Subject: Re: Handles for Public Functions
Message-ID: <8901032009.AA00407@LYRE.MIT.EDU>
Date: 3 Jan 89 20:09:41 GMT
References: <7098@batcomputer.tn.cornell.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 14


    Date: 3 Jan 89 18:10:38 GMT
    From: gdykes@tcgould.tn.cornell.edu  (Gene Dykes)

    My solution is to require widgets with public functions that
    desire to be "nice" widgets to return a list of tags and function addresses
    as the value of a resource (I chose "XtNpublicFunctions").

This is certainly a viable approach.  If you were concerned about
the extra space in each widget instance you could implement this
as a virtual resource with a get_values_hook procedure.  An
alternative is to encourage widgets to implement an action proc
corresponding to each public function and register them in
the class actions list.