View Single Post
Old 05-03-2019, 07:34 PM   #713
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,848
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by Toxaris View Post
The reason is why you see the high usage in that case (the scrolling) is also explainable. It is not because of that loop though. When a mark is found, it will look for the next one. It does that by moving character for character until there is a hit. That causes the high usage of Word.
Devil's advocate questions

IMO the user doesn't need to see the scrolling. So, can the looking be done 'invisibly'? If I take focus away from Word while DC is scrolling I've had it crash - horribly.

Rather than looking at every character, could you get Word to find the next 'mark' -- up or down as case may be?

BR
BetterRed is offline   Reply With Quote