dheller@cory.Berkeley.EDU (Dan Heller) (06/15/89)
I have now run into enough cases where I need this functionality, that I can no longer think of workarounds. What I need to do is get certain resource values about a widget that I am *about* to create. All the current functions like XtGetResources require having a widget already and passing it to the routine. I want to know some of these values before I create the widget. Many times, I just want to know info about the widget -class-, not an instance --does this make the problem easier to solve? To put it another way, I'd like to call a function which the widget-creation machinery calls that initializes a resource structure -- but avoid creating the widget. Dan Heller <island!argv@sun.com>
swick@ATHENA.MIT.EDU (Ralph R. Swick) (06/16/89)
> I have now run into enough cases where I need this functionality, that > I can no longer think of workarounds. What I need to do is get certain > resource values about a widget that I am *about* to create. There is no pre-packaged function that will do this all at once for you. Most of the pieces you need to build such a function do exist. See XrmGetResource and XtConvert.