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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2350.0. "need to disable some session mgr (sub)menues" by BERN01::RUGGIERO () Mon Feb 26 1990 04:35

Another problem...

I need to set up some sort of captivness on a DECwindows account. The user
should not have any access to the following session manager's customize menus: 
Applications definitions, Applications Menu, Define Startup, Security,
and Sessionmanager.

From previous DECwindows version I have a DECW$XDEFAULTS.DAT with which I 
could disable some Menues. This file is not valid any more under VMS5.3.
The disable Session manager and the disable security still work, but what
are the button names for the other menues?

I read somewhere (was it in the release notes?) that the use of DECW$XDE...
should be avoided. Is there a better/another way?

thanks

---markus---
T.RTitleUserPersonal
Name		DateLines
2350.1Session Manager menu resource namesSTAR::BROUILLETTEThu Mar 08 1990 17:0336
    
    Here are the names for V2.  The names may change in the future. 
    Making these buttons insensitive in a decw$xdefaults file is not
    supported and may not work in future releases.
    
    There is no supported way in V2 to get a captive account.  We know
    there is a BIG demand for this feature.  We are working on solving this
    need in a future release of DECwindows.
    
    	Session Menu:
    
        Pause = PauseButton
    	Quit = QuitButton
    	
    	Customize Menu:
    
    	Application Definitions = AppDefButton
    	Application Menu = AppMenuButton
    	AutoStart = AutoStartButton
    	Keyboard = KeyboardButton
    	Languages = InternationalButton
    	Pointer = CursorButton
    	PrintScreen = PrinterButton
    	Security = SecurityButton
        Session = SessionButton	
    	Window = WindowButton
    	Use Last Saved Settings = UseLastButton
    	Use System Defaults = UseSystemButton
    	Save Current Settings = SaveCurrentButton
    
    	Print Screen Menu
    
    	PrintEntireButton
    	PrintPortionButton
    	CaptureEntireButton
    	CapturePortionButton
2350.2this may be obvious but...STAR::BROUILLETTEThu Mar 08 1990 17:075
    
    Remember that the user's decw$xdefaults.dat file is read and merged
    last when resource files are loaded.  So, if the user can get to that
    file and change it, they can "uncaptivate" their account.
2350.3thanksBERN01::RUGGIEROFri Mar 09 1990 05:1617
re .2:
Yes, I am aware of that, and I am trying to prevent the user from messing
around with this file.

re .1:
Thank you for the resource names. I alread found them by just dumping the 
.UID-file and lloking what's in there. Nevertheless your list tells me that
I found the right stuff - and it works.

Thanks again


---markus---

Markus Ruggiero
EIS/PublicSector
DEC Z�rich
2350.4An example pleaseSNOC01::NICHOLLSElvis lives only in an anagramThu Mar 15 1990 01:034
    Could someone please give an example of disabling the de-sensitizing
    the Quit button, please, as an example of how to do what is in .1?
    
    Michael
2350.5here's the exampleBERN01::RUGGIEROThu Mar 15 1990 03:5813
I finally did it. Here is the DECW$XDEFAULTS.DAT I constructed.


*AutoStartButton.sensitive:		False
*AppMenuButton.sensitive:		False
*AppDefButton.sensitive:		False
*SecurityButton.sensitive:		False
*SessionButton.sensitive:		False
*UseSystemButton.sensitive:		False



---markus---