nisus.com

I’m using NWE 2.5, OS 10.3.9, original flat-panel iMac.

I was getting a real word hash; part of it was that Nisus seemed to clash with Spell Catcher‘s auto-suggest, so I have turned off Nisus’s auto-completion/suggestion feature and its “Check spelling while I type.” However, if I type at all quickly, letters come out transposed, sometimes repeated.

Any suggestions?

Thanks,

Hi Cynthia, I would try disabling Spell Catcher as that is probably the cause of the problems. It is possible that the "trick" they use to insert their feature into every application does not play nice with Express. If disabling Spell Catcher solves your problem I would write to them about the incompatibility.

martin wrote:Hi Cynthia, I would try disabling Spell Catcher as that is probably the cause of the problems. It is possible that the "trick" they use to insert their feature into every application does not play nice with Express. If disabling Spell Catcher solves your problem I would write to them about the incompatibility.

Hi there,

A mutual customer pointed me to this post (the trouble he was having with NWX and Spell Catcher was most likely not the same as what's described here), thought I'd clarify a couple of things and ask a question or two...

First off, Spell Catcher X does not use any sort of "trick." It's a by-the-book Mac OS X input method, and as such uses only public, documented, standard APIs and techniques to do what it does.

And yes, it's definitely the case that if both NWX and Spell Catcher are configured to perform the same function (smart quotes, completion, automatic correction) you can get incorrect results when you type something that causes both of them to modify what you've typed on-the-fly. The solution is simple, just disable the equivalent feature in one or the other - make sure they aren't "battling" in any way.

Cynthia: Can you reliably reproduce the problem with transposed characters when typing quickly? Does the problem disappear if you choose a keyboard (flag icon) from the input menu (deactivating Spell Catcher's input method)?

Any chance this only happens when you type something that causes Spell Catcher to make some sort of Automatic Change, expansion or correction (smart quotes, automatically capitalize, en-em dashes, etc.)?

If you can pin this down a little more, I'd be grateful. If it's actually my problem, I definitely need to fix it.

ALSO: Make sure you are using the latest version of Spell Catcher X (version 10.2.1).

Note that I do have a number of beta testers that use NWX as their primary WP, and I've never had a report of something like this. Certainly not any sort of known problem...

Evan Gross wrote:First off, Spell Catcher X does not use any sort of "trick." It's a by-the-book Mac OS X input method, and as such uses only public, documented, standard APIs and techniques to do what it does.

I apologize for my quick uneducated words. I wasn't aware how Spell Catcher accomplished its features.

I'm going to write to you privately to see if there's anything I can do to help you and your customers.