[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

891.0. "PROB: IMPM Attr Name Labels Mispositioned in Set window" by COOKIE::KITTELL (Richard - Architected Info Mgmt) Tue Apr 09 1991 18:03

V1.1 SSB

Under certain conditions, the labels for the attribute names in the Set
window overlap. In particular when attribute names are long and are
wrapped. Not enough vertical offset is applied, and the wrapped part of
the name overlaps the name of the next attribute.

This is much easier to look at than describe. Snag the two files listed
below and run them through the CDA viewer on your workstation. The Show
file is a capture of the Show window for the same attributes, which
doesn't have the wrapping problem, probably because it doesn't need room
for the Send buttons.

	COOKIE::AIM$PUBLIC:[AMI]SET.DDIF
	COOKIE::AIM$PUBLIC:[AMI]SHOW.DDIF

Note that the directory name isn't a typo, it is an acronym for AIM
Management Interface. An unfortunate choice, given our group name.

T.R	Title	User	Personal Name	Date	Lines
891.1	re wrapping problem	VERNA::V_GILBERT		`Tue Apr 16 1991 12:13`	11
	Richard, Are you having this wrapping problem on a SET window when it is first displayed, or after resizing the window, or after starting an operation, or after expanding a field? Can you give me more information as to the sequence of events which cause the wrapping of attribute names. Thanks, Verna
891.2	info	COOKIE::KITTELL	Richard - Architected Info Mgmt	`Tue Apr 16 1991 18:13`	16
	>Can you give me more information as to the sequence of events which cause the >wrapping of attribute names. Verna, 1. Select Set Characteristics from the Operations list box. 2. The Set window appears. The attribute names visible are short enough that no wrapping occurs. 3. Scrolling the window down exposes the two attributes whose names wrap. The COOKIE::AIM$PUBLIC:[AMI]SET.DDIF file is the capture of the window at this point. No resizing, operations, or field expansion.
891.3	Maps appear differently on hi-res / lo-res monitors	CUJO::HILL		`Fri Apr 26 1991 23:50`	27
	I have seen something similar to a wrapping problem when I try to display a map built on a VAXstation 3100 Model 48 on a VT1300 Graphics head with higher resolution. The Icons are somewhat distorted and they overlap the text. Crude Example: On VAXstation 3100 --------- .dna_node.MYNODE \| NODE4 \| --------- On VT1300 hi-res monitor --------- .dna_node.MYN\| NODE4 \| --------- By the way, I used the following commands to display DECmcc on the VT1300 (VTNODE) from my VAXstation 3100 (MYVAX): MYVAX_$ SET DISPLAY/CREATE/NODE=VTNODE MYVAX_$ SPAWN/NOWAIT MANAGE/ENTERPRISE/PRESENTATION=MCC_ICONIC_MAP_PM NOTE: Be sure you have allowed access via the Management Window's CUSTOMIZE Pulldown menu, SECURITY optioon. -Dan
891.4		TOOK::F_MESSINGER		`Sun Apr 28 1991 19:38`	8
	Dan, I believe you may correct this by restarting your server, specifying "75 DPI". Fred
891.5	Suggestion for high resolution monitor output.	CUJO::HILL		`Sun May 12 1991 15:25`	10
	Fred, I understand what you mean. Editting SYS$COMMON:[SYSMGR]DECW$DEVICE.COM parameters DECW$MONITOR_DENSITY and DECW$SERVER_DENSITY should do the trick, but this seems like a real waste of high resolution monitor capabilities. Would it be possible for DECmcc to determine the monitor/server resolution and adjust the output accordingly by using an offset of some sort to match what is coming from the map file? -Dan
891.6		TOOK::F_MESSINGER		`Mon May 13 1991 08:12`	5
	Dan, The problems are/will be fixed for V1.2. The changing of the font density was meant as a short term "fix". Fred