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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

2520.0. "customization of map alarm color " by HKGACT::SUSANCHAN () Tue Mar 10 1992 01:48

Is there a rule to change the map alarms color through the Iconic Map?

Customize --> Maps --> Alarms   then the "Customization - Map Alarms Color" 
window pops up.  

After I change the color of "Critical" and click APPLY.  A DECmcc Map Window 
Message pops up: "Invalid Color entered for Major severity".  So I change the 
color of "Major" and click APPLY.  Another DECmcc Map Window Message pops up: 
"Invalid Color entered for Minor severity".  And so on and so forth, until I 
change all the default severity color.  

Is that a known "features"?  

Afterall, I found interesting that after I have changed all the default 
severity color, I can change any of the severity color in any sequency without 
any error messages.  Why?  What make the default severity color so different?


BTW, it is BMS V1.1 and VMS v5.3-1.


Also, can anyone explain my previous note about toolbox went blank after 
registered a node4 successfully.


Thanks & regards,
Susan Chan
HKEIS
T.RTitleUserPersonal
Name
DateLines
2520.1TOOK::R_SPENCENets don't fail me now...Fri Mar 13 1992 10:0714
    I have no idea about "blank toolbox". I have never seen that.
    
    The problem described here is a BUG. The problem is that the
    default resource file, DECW$SYSTEM_DEFAULTS:MCC_RESOURCE.DAT,
    has the colors for the alarm severities in all lower case and
    DECwindows insists on the case exactly matching the named DECwindows
    colors, in this case, with a leading uppercase character on each word.
    
    What you did was fix them the hard way. Sorry. WHen you changed one
    color and APPLIED it, the system checked to see if the chosen colors
    were valid and it flagged the first one it found that didn't match...
    
    This is fixed for V1.2
    s/rob