And it was a very stupid thing for OpenMotif to do. Using XtNameToWidget
is fraught with potential for getting the wrong widget, especially when
the base widget allows the application to add widgets. What happens if
the application adds a new child - even a dialog - that it names "Help"
? It is arbitrary as to which widget would be returned. I know, the
programmer should name it something else, but the potential is there,
and such a "bug" would be very, very difficult for most programmers to
The whole point of all of the Xm...GetChild() functions was to ensure
that there was an easy, efficient, and foolproof way to obtain specific
children of a composite, without having to search through the quarked
names of all of the children.
Eliminating any of these convenience functions is a terrible idea.
Fred L. Kleinschmidt
Boeing Associate Technical Fellow
Technical Architect, Common User Interface Services
M/S 2R-94 (206)544-5225