NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/sys/next/software/3594

Internet Message Format | 1993-01-23 | 1.9 KB

Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!usenet
From: [e-mail] (Izumi Ohzawa)
Newsgroups: comp.sys.next.software
Subject: Re: Framemaker character update is SLOW, any solutions?
Date: 23 Jan 1993 02:12:08 GMT
Organization: University of California, Berkeley
Lines: 27
Distribution: world
Message-ID: <1jq9ho$[e-mail]>
References: <[e-mail]>
Reply-To: [e-mail]
NNTP-Posting-Host: moica.berkeley.edu

In article <[e-mail]> [e-mail] (Bill Punch) writes:
>I have a NSC(non turbo), running 3.0 with 32 Megs of memory and a dedicated
>100Meg swap disk. Despite this wonderful setup when I type to Framemaker (3.01)
>there is a noticeable delay between keystroke and screen appearance. If you type
>quickly (60 wpm) it is terribly distracting to watch the screen, you are
>typically 1-2 characters behind.
>
>Any reason for this slowness? Any solutions?

For FrameMaker,
you will get dramatic speed improvement on NSC if you select a small bit
of text, set its text color to something that is not black/gray/white, and
then set it back to black again.  That is all you need to do.
But unfortunately you have to do it for each document each time you open it.

By doing the above, the window depth gets promoted to match the VRAM
organization.  This makes things much faster although you consume more
memory for backing store.  Unless your document contains colored items,
FrameMaker creates 2-bit gray windows on all machines initially.
This is not true with WordPerfect, which opens all documents (even if
you don't use color) with window depth matched to the display hardware.

--
Izumi Ohzawa             [ $@Bg_78^=;(J ]
USMail: University of California, 360 Minor Hall, Berkeley, CA 94720
Telephone: [phone]     Fax:  [phone]
Internet: [e-mail] (NeXTMail OK)