[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

3937.0. "Disabling map modification ?" by ROM01::PROFETI (Livia EIS Rome) Wed Oct 21 1992 14:34

    Is there any possiblity to disable MCC maps modifications ?
    
    I'm looking for a read-only map feature, not in sense of data (see note
    1330), just in sense of screen modification.
    
    For my customer that seems to be the major DECmcc problem, I agree with
    anyone says that's is a stupid thing, but my customer is seriuosly 
    thinking not to buy DECmcc for that problem ...
    
    The problem is that people is not so able to manage the mouse and they
    modify the maps any click they make with the mouse. 
    
    I know the version 2.0 should have new features to customize DECmcc user
    and that seems to be a great new, but isn't possible to have any
    pre-feature for the 1.3 (Motif ?).
    
    Thanks for any new and for any suggestion to solve this problem as soon
    as possible (workaround should be very appreciate).
    
    Livia

T.R	Title	User	Personal Name	Date	Lines
3937.1	it's in 1.3	TOOK::MCPHERSON	pre-retinal integration	`Wed Oct 21 1992 23:45`	3
	What you are asking for "(map lock") is already in the 1.3 release. It works. /doug
3937.2	Good !	ROM01::PROFETI	Livia EIS Rome	`Thu Oct 22 1992 08:18`	7
	Wonderful, I think the customer will accept to wait for a few months. Can you tell me how it's implemented ? For example if it's a matter of user customization or whatever ? Many thanks for your quick reply. Livia
3937.3	simple.	TOOK::MCPHERSON	pre-retinal integration	`Thu Oct 22 1992 09:38`	4
	You just click on the picture of the padlock at the top of the screen. Easy enough? /doug
3937.4	MB1 doesn't drag either	MCC1::DITMARS	Pete	`Thu Oct 22 1992 11:24`	14
	Because V1.3 is Motif, MB1 (which is what you're always pressing to select things) is NOT the button used to drag things areound. You use MB2 to do that. This is Motif compliant behavior. It also almost entirely prevents accidental modification of the map, even without the fun padlock. p.s. In V1.3, MB2 is also the button used to "drop" entities on the map during an Add operation. I mention this only because it took me a while to get used to it, and I expect it will take other map users a while too. Be prepared! :^)
3937.5	Digital understands the problem	SKIBUM::GASSMAN		`Thu Oct 22 1992 12:29`	11
	One thing MCC should probably look into in future releases is the MSU approach to security of functions. In the next release, there are 16 privledge bits, each tied to a function. Each remote map user has a profile indicating which functions they can use. SET can be disabled, DECnet or bridge can be disabled, map editing can be disabled. In addition, events are generated when the map is edited, allowing the event log to show what occured and by which user. These are features which customers have been asking for - so some joint engineering effort may be useful in this area for follow on MCC releases. bill
3937.6	Privileges/Protections are an absolute MUST	CUJO::HILL	Dan Hill-Net.Mgt.-Customer Resident	`Sun Oct 25 1992 01:51`	13
	The privs/protection mechanisms Bill describes are a must for my customer. There are already many types of users who require different privs. My customers have been asking for Map Lock and Protection schemes for two years. I've been hearing some good things about V1.3. This is just another piece of good news. Believe it or not, being able to lock the map (and other seemingly small issues) is actually a rather big item for some customers. By the way, is MSU still in parallel development with DECmcc/EMA? -Dan