Hi Don:
You are correct, updating the display doesn't need the CPU for "long". It
only needs a couple of microseconds. The problem is that Word has to wait
too long before OS X gives it that time!
Some people have discovered that clicking the mouse will hurry things up.
You click once, the mouse generates a high-priority interrupt that takes one
microsecond to deal with, but on the way back from dealing with it, the
system will return control to Word long enough for it to do what it was
waiting to do.
Doesn't work for everyone in every circumstance, but may be worth trying for
you.
Just a note to others:
We've said several times that Microsoft is working on a fix for these
issues. Let me say it one more time: Microsoft is working really really
hard on a fix for these issues. What they need right now is lots and lots
of detail about how you got into the situation: exactly what you clicked,
toggled or scrolled for about 30 seconds back from the slowdown, and what
you see.
There are several parts of the code involved here: some belong to Apple,
some belong to Microsoft. Both companies are currently working on the issue
and need all of the detailed input they can get. In other words: seeing
lots of users saying "Hey, I've got that problem too..." is a bit
frustrating. They need users to stick with the problem the way Don has done
in this instance, supplying lots of detail.
Cheers
Hi John,
OK, yes, I agree that this is a delicate balancing act. However, there
clearly is something wrong with the behavior of Word 2004 with Endnote
fields, because the scrolling freezes for seconds, or until I click on the
title bar of the window. This doesn't happen in Word v. X. I can't imagine
that updating the display needs to grab the CPU for that length of time!
Don
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <
[email protected]>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 4 1209 1410