[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

2352.0. "changing colors (colours) with Hubwatch" by KERNEL::MCSKEANEP (one bit brain with parity error) Wed Jun 07 1995 15:27

    
    Can anybody figure out the following behaviour in Hubwatch V4.0.1
    running under OSF V3.2
    
    I've copied /usr/kits/HUBwatch/Hubwatch_teal to my home directory and
    renamed the file Hubwatch. If I fire up Hubwatch from my own directory,
    the default agents file is found but when the hub is displayed, I still
    get the default tan colours in the display. If I click on a module, then
    I get the highlighted teal colour. If I click on LAN interconnect then
    the screen background remains tan but the module icons come up teal. 
    
    I though that if I had the teal defaults in my own directory then the
    hub should come up in teal, The only way I could get the whole hub to
    come up in teal was to copy /usr/kits/HUBwatch/Hubwatch_teal to
    /usr/lib/X11/app-defaults/Hubwatch.
    
    Thanks in advance,
    
    POL
T.RTitleUserPersonal
Name
DateLines
2352.1Check XENVIRONMENTSTEVEV::VINGERHOETThu Jun 08 1995 12:367
Check to see if the environment variable XENVIRONMENT is set. This will
set the default directory where resource files are found.

Most people just stick the Hubwatch file into their home directory and
ignore XENVIRONMENT.

Steve
2352.2ProbeWatch causes HUBwatch Color Problem....NETCAD::SKABOExpect Nothing U never disappointedThu Jun 08 1995 14:5413
    
    	The HUBwatch Color change problem that Paul McSkeane is seeing is 
    because of a environment setting caused by ProbeWatch on his system. I have 
    experienced the same problem in systems test, so I will be entering a QAR 
    with this problem and talking with Jack Forrest (ProbeWatch Product 
    Manager).

    	The setting is that is in the ProbeWatch set up: 
    	
    		"setenv XUSERFILESEARCHPATH /usr/kits/PROBEwatch/X/%N"


    Tom Skabo - HUBwatch Systems Test