ITEM: BA4389L

NetView V3.1 & SystemsMonitor V2.1 > Xresources questions/problems

Question:

cde information
General set up anfd functionality of it

Response:

Env: AIX 3.2.5

Desc: Greg needs some help configuring CDE

Act: I showed Greg how to change colors via the style manager as well
as how the home session worked. I also showed him how to work
with basic front panel customization using 'drag and drop'
functions. Greg also needed help configuring the .profile to
read in his .kshrc .

There was a slight problem in that if the Netview GUI was up
when the home session was set, Netview would spawn about 5
sessions when CDE was reopened. The only way around this was
to close the netview gui before saving the home session.

Next: Greg was also having troubles setting Netview resources. I showed
him how to use the xrdb, but this didn't seem to work. He
will try some more on his own, and if he still has problems,
he will contact NV6K.

Response:

ENV: RISC/C10; AIX 4.1.3; Netview V3.1;
DES: Netview was running fine with correct color on the pull-down
menu. However, after CDE was installed, the color on the
pull-down menu was no longer black on pink but now it is
white on pink. Spoke to the GRAPH specialist and he said
that DCE doesn't read /usr/lib/X11/app-defaults.
ACT: All defaults for Netview is defined in /usr/OV/app-defaults
directory. The file /usr/OV/app-defaults/OVw contained
the following default information that customer might want
to verify or change:

! Defines the EUI MainWindow background color
OVw*mainWindowColor: gray

! Defines the EUI MainWindow menu background color
OVw*mainWindowMenuColor: gray

! Defines the EUI MainWindow status1 and status2 color
OVw*mainWindowStatus1Color: gray
OVw*mainWindowStatus2Color: gray

! Defines the EUI MainWindow Message area frame color
OVw*mainWindowFrameColor: gray

NXT: Research further then call back.

Response:

Act: The customer was having some problems with
getting the Xresources correct for SystemsMonitor
and NetView, specifically the text/foreground for
both of these. They are comming up in CDE as pink
with white lettering. It was necessary to search in
the /usr/OV/app-defaults directory in the OVw file
to determine what the correct statement is. As it
is there is no mention nor does the string/resource
exist in the app-defaults directory. Here is the
resource string necessary for "foreground" text:

OVw*foreground: \.

And the one for SystemsMonitor:

SMconfig*foreground: \.

By using these strings you can change the font color for
the SystemsMonitor configuration panel and the OVw
ipmap EUI. If there are "text color" problems with either
of these two applications and CDE then one work around for
this is to specifiy these in either the users' .Xdefaults
file or the app-defaults file for the application.

Next: Customer agreed to close the call

Response:

Closing with Customer Approval

Response:

Closing with Customer Approval

Response:

Act: After doing some research I have found that
the SMconfig with an "*" tacked on to it should have
changed all of the child windows that the SystemsMonitor
configuration application spawns. I do not know why
this is not working for the customer. I will have
to confirm what release or "level" of AIX 4.1.X the
customer is at to see if he has recieved the refresh of
CDE. I so then I will need to test this on a machine
with this exact level of AIX.

Also there are several panels where text can be entered
that are turned "light gray" by default and I have not
been able to isolate these resources. The only other
thing that I can think to do is to have the customer
enter 16 different entries in his .Xdefaults to
explicitly determine what each child SystemsMonitor window
should appear as. Although one should not have to do this;
by simply specifiying the entire SystemsMonitor class
identifier--SMconfig--all windows should change! The
other thing that I have noticed is that within the
app-defaults file there seeems to be mention of a
SystemsMonitor resource application. I am going to
check and see if this is an interface into Xcustom
or perhaps is this a separate application.

Next: Call the customer back and give him the information
that I have discovered, and continue to test this issue further.

Response:

Env: AIX 414 and Systems Monitor for AIX 21
The customer will be upgrading to the newer
release of Systems Monitor very soon.

Act: I have worked with the custom program that is available
with Base AIX 3.2.5. This did find the correct class, but
there is still a problem with finding the resources for
the textual windows in the SystemsMonitor configuration
application.

Next: continue to research.

Response:

ACT: You are still seeing your pulldown menus with
white letters on blue background, instead of black on
blue.

Next: Inform Mike that you having this problem.

Response:

Calling customer

Response:

Act: I have called the customer and asked him for
information on the level of SystemsMonitor that is
installed on his machine with the configuration panel
on it.

Next: Wait for customer to call in with this information.

Response:

Act: I have tested this on a 4.1.3 machine and there appears
to be a problem here with the way that the foreground
is specified. When bringing up the interface the text
came up as white while the background came up as light
gray. After setting the SMconfig variable I was able
to set the text correctly.

Next: Call the customer back and see what he has done.

Response:

Calling customer

Response:

Not In, Left Message

Response:

I don't know what needs to be done with this item--LM for Douglas Floyd,
TL 793-6932, to review this since it appears he routed the item to
SFINFO.

Response:

Act: I really don't know or why this item was put in my queue. This
was apparently one of the NV/6000 folks.

Next: RQ to NV/6000 for closure.

Support Line: NetView V3.1 & SystemsMonitor V2.1 > Xresources questions/problems ITEM: BA4389L

Dated: January 1996 Category: N/A

This HTML file was generated 99/06/24~13:30:23

Comments or suggestions?
Contact us