The reported slow behavior is not something that is believed to be
addressed by the latest build, but we've sent one out to Garry just
to make sure.
Generally we use the following procedure to find and fix problems.
The first step is to make sure the situation is not caused by a
misunderstanding of the program's operation. The next step to
to try to get the problem reproduced here. This requires that you're
able to determine the sequence of actions that cause the problem to
appear. We may suggest experiments for you to run to try to find
out what the problem is sensitive to. It can sometimes be a
challenge to figure this out, but once we have the problem in captivity
we can fix it. Lastly, sometimes we may ask you to send us your
deed file so we can examine it, though this isn't very common.
The main point in this is that we need to reproduce the problem before
we can fix it.
----- Original Message -----
From: John Lyon <JCLyon(a)compuserve.com>
Sent: Monday, December 04, 2000 8:58 PM
Subject: Re: [DMU] pushing the limits
Message text written by Steve Broyles
>Heavy use of annotations might conceivably have an effect on display
I might add as a "power user" that I typically use a 300 MHz Gateway
notebook with only 96M RAM and have had no problems of any of the
kinds with Build 20. My project involves four different data bases,
ranging from 1300 to 2500 tracts. In earlier builds I experienced some
scrolling, occasional freezeout/crashing problems and other display
peculiarities (loss of color in the tracts) which I guessed had to do with
annotations, which I'd started to use with greater frequency. But this
went away with Build 20. All commands respond instantly (faster
So performance isn't an issue, at least here. I'd suspect
Shop Ancestry - Everything you need to Discover, Preserve & Celebrate