Thank you for the hint! Our developers will investigate this problem.
Sven and girivs...
This problem seen by girivs
also applies to trying the exact same "method" in TM2010 as well.
However, there are easier ways to do this "replace all with x (or whatever)"... but the Developers might want to look into the current situation still.
I remember long ago that MS Word 2003 and 2007 tended to NOT like this current method well, either, generating occasional, although some might say more rare, lockup's and wildly excessive CPU load.PERSONAL Opinion:
However, there MIGHT be no sense to correct anything in TM2008, but perform any tweak or code-correct in TM2010 and of course in anything that comes later.
TM2010 clearly LOOKS like TM2008, but the ideas and advancements since 2008 are quite numerous.ONE IDEA:
Instead, add a function -- maybe call it "Crossout -- perhaps IN Search and/or Replace that allows any amount (within reason) of ALREADY SELECTED text to automatically be replaced with any other character (within reason) where spaces are treated as non-replaced spaces, etc. so that ONLY characters get replaced with "x" for example.
I have seen a very few apps do it that way, but those that did completed very fast, and without any memory or other unusual problems and end-users were a lot happier.