Spell Check Continues to Flag Words as Misspellings

Paul Solt's Avatar

Paul Solt

10 Apr, 2018 03:20 PM

Spell Check keeps telling me words are misspelled.

It's really annoying, I'm not sure why, but it's been happening for 6-12 months at least.

I have to double click the word to make the underline misspelling thing go away.

When I leave focus on the window, the underlined error goes away. IN this screenshot I misspelled "spelling" and then it fixed it, but the problem remains underlined.

  1. Support Staff 1 Posted by Fletcher on 12 Apr, 2018 12:21 AM

    Fletcher's Avatar

    Paul,

    My apologies -- I drafted a response yesterday but it seems to have
    disappeared and apparently was never sent.

    Short version -- Apple's NSTextView/Core Text API is powerful, but there
    seem to be a few gaps. One of which affects spelling. In order to get
    Composer 4's faster syntax highlighting to work I have to override
    certain aspects of NSTextView. In doing so, I discovered (or more
    likely one of my users... ;) that spelling and related features were
    disabled. There is no obvious way to "just enable them." It required
    manually re-implementing the logic to automatically check spelling, and
    I'm 1000% certain the algorithm I came up with is not exactly like
    Apple's. I would love to have macOS handle this automatically, like
    Composer 3, but that breaks other things....

    That said, I can't replicate the behavior you describe. Whether I
    automatically correct spelling mistakes or manually correct them, the
    underlining goes away.

    UPDATE: More testing -> I can occasionally replicate it with automatic
    spelling correction, but it seems to happen only with certain words or
    certain circumstances, and I'm not sure what those are. Perhaps if I
    can nail down what triggers the behavior I can fix it.

    Additionally, when it does happen and I continue typing additional words
    in the same sentence, it does go away a couple of words later.

    I'll try to dig into this more in the next week or so. If you find
    anything consistent between when it works properly and when it doesn't,
    please let me know.

    Fletcher

  2. 2 Posted by Paul Solt on 13 Apr, 2018 08:27 PM

    Paul Solt's Avatar

    I'll try and record something the next time I'm writing so that you can see what I'm typing and the results.

  3. Support Staff 3 Posted by Fletcher on 24 Apr, 2018 07:29 PM

    Fletcher's Avatar

    Long explanation short -- early in development, it seemed that I had to override a core piece of Apple's text view code. Which meant I had to write a bunch of workarounds to get other core Apple functionality to work (including spelling).

    I think I was able to correct an underlying assumption, which now allows me to use more of the core Apple code, which means that I can now revert to built in spelling/grammar. Which means that these sorts of things should now work better.

    This will be included in version 4.4, assuming nothing else is broken in my testing!

    Thanks for your patience!

    Fletcher

  4. Fletcher closed this discussion on 24 Apr, 2018 07:29 PM.

  5. Fletcher re-opened this discussion on 01 May, 2018 12:51 PM

  6. Support Staff 4 Posted by Fletcher on 01 May, 2018 12:51 PM

    Fletcher's Avatar

    I posted a 4.4 beta release that should fix spell checking, as well as a few other things. Once it's been tested, it will be pushed out for general use:

    http://support.multimarkdown.com/discussions/betas/384-composer-44-...

  7. Fletcher closed this discussion on 01 May, 2018 12:52 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac