chapman@lll-lcc.UUCP (Carol Chapman) (10/26/89)
I've been trying to take as many resources as possible out of my code and put them into /usr/lib/X11/app-defaults/<class>. Some resources such as Fatrad*Label*borderWidth: 0 seem to work fine, but some of the resources for positioning within an Athena form widget appear to be ignored. For example, Fatrad*colorbar_label.fromHoriz: NULL and/or Fatrad*colorbar_label.horizDistance: 5 are ignored. I'm having similar problems with Athena text widget resources, although I have not yet been able to verify if this is related to one particular text resource such as textOptions, or if it is related to all text resources. Am I doing something wrong, or are there limits as to which resources can be listed in an app-defaults file? thanks, carol -- ------------------------------------------------------------------------------- Livermore Lab (chapman@lll-crg.llnl.gov or chapman@lll-lcc.llnl.gov) P.O. Box 808, L-153 Tel. (415) 423-7876 Livermore, CA 94550 "Never own anything that you have to FEED or PAINT."
converse@EXPO.LCS.MIT.EDU (Donna Converse) (10/26/89)
> some of the resources for positioning within an > Athena form widget appear to be ignored. For example, > > Fatrad*colorbar_label.fromHoriz: NULL and/or > Fatrad*colorbar_label.horizDistance: 5 In resource files, the Athena Form resource "fromHoriz" is used to specify placement of a child widget of the Form, as you already understand. The string value of the resource specfies a widget name, which must be a widget which is an (already created) child of the Form. What your resource specification says here is to place the colorbar_label widget 5 pixels horizontally from the widget named NULL. Understanding this should help you to get things working right. Donna Converse converse@expo.lcs.mit.edu
kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) (10/27/89)
> I'm having similar problems with Athena text widget > resources, although I have not yet been able to verify if this is > related to one particular text resource such as textOptions, or if it > is related to all text resources. The Text widget is a little unique with respect to resources. 1) Several of the resources operate on the Sink or Source assocaited with the text widget. This means that "foo*Text.font" will not work, you should use "foo*Text*font". The documentation is unclear as to which resources are properties of the source or sink, so you may have to experiment a little, in 99% of the cases it is safe to always use "Text*<resource name>." 2) TextOptions does not have a converter to convert strings to TextOptions, so there is no way to specify text options in a resource file. Both of these problems will be fixed in R4. #1 with documentation, and #2 with new code. Chris D. Peterson MIT X Consortium Net: kit@expo.lcs.mit.edu Phone: (617) 253 - 9608 Address: MIT - Room NE43-213