| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 4043.1 |  | VERNA::V_GILBERT |  | Fri Nov 06 1992 10:37 | 5 | 
|  | At this point (including V1.3), it is not possible to disable menu bar entries
from the Iconic Map window.  You may add applications using launch but cannot
currently disable.
Verna
 | 
| 4043.2 | Disable menu bar item should have been a requirement | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Mon Nov 09 1992 23:35 | 8 | 
|  |     Hi, Verna,
    
    Too bad this didn't make it into the V1.3 release.  I'll place a note
    in EMF_REQ notes file.  Customers want this, especially those who have
    multiple groups with different levels of expertise and responsibility
    managing the network.
    
    -Dan
 | 
| 4043.3 |  | ZPOVC::GEORGEKOH |  | Sun Apr 18 1993 23:18 | 10 | 
|  |     Hi,
    
    Is there a way to disable the menu bar before the next distance release?
    Customer does need it urgently.
    
    Hope someone can provide some inputs.
    
    Thanks,
    George.
                             
 | 
| 4043.4 | Product management for requirements | TOOK::MINTZ | Erik Pavlik Mintz | Tue Apr 20 1993 07:29 | 4 | 
|  | This is better suited to the NOTED::EMF_REQ conference or directed
to product management.
-- epm
 | 
| 4043.5 | Still not possible??? | ARRODS::GILLJ | John, DTN 847-5849 | Fri Nov 05 1993 11:15 | 11 | 
|  |     
    My customer wants to ensure that his MCC Applications menu enables his
    network operators to launch HUBwatch but not run any of the
    Autotopology applications. 
    
    Am I correct in assuming it is still not possible to do this?
    
    Regards,
    
    John
    
 | 
| 4043.6 | relocate all your .def files appropriately. | TOOK::MCPHERSON | Imagine whirled peas. | Fri Nov 05 1993 12:43 | 15 | 
|  | re .5
If I remember correctly, mcc_appl_<mumble>.def files are used to define the
contents of the "Applications" pull-down menu, as it ships on the kit.
The way to customize the behavior of "who can see what on their pull-down
menu", is to put all the mcc_appl_*.def files somewhere *other* than in the
default "mcc_system" location and create PER-USER versions of the
MCC_APPL_SYS_LOCATION and MCC_APPL_USER_LOCATION logical/environment variables
to point each user to the appropriate collection of .def files.
See chapter 8 of the "POLYCENTER Frameworks and Appilcations Use" manual for
more information.
/doug
 | 
| 4043.7 | Sensitivity Resource for Cascade Buttons ? | VNABRW::HAINZL_R |  | Wed Dec 22 1993 09:29 | 14 | 
|  | One of my Customers (Air Traffic Control Austria) has the same requirements as
.0 and .3 :
I'd like to test the XmNSensitive-Resource (Motif Core Widget Set) -
	if not somebody else did it already:
for this test the Widget Hierarchy used in MCC (including Class and 
Instance names) would be necessary. Since I have no time dumping through the
.UID and .EXE Files ...
   could somebody provide this information (as far as I know there is no
documentation on this subject - and also no detailed  information on
MCC_RESOURCES.DAT )...
Richard Hainzl
 |