Lion compatibility
#1
Posted 09 July 2011 - 09:13 PM
#2
Posted 09 July 2011 - 09:31 PM
Allen Watson, on 09 July 2011 - 09:13 PM, said:
Earlier versions of Spell Catcher X aren't totally compatible with Lion, as numerous changes were made to the way the Input menu works (for all input methods). These changes were (of course) dealt with in Spell Catcher X 10.4.
#3
Posted 22 July 2011 - 03:04 PM
Shortcuts appear to work fine in Google Chrome and they worked fine on Snow Leopard and Safari 5.1 so it's something going on with Lion and Safari.
*UPDATE*
It appears that the problem is using Mac OSX 10.7 (Lion), Safari 5.1 and WordPress. When trying to use shortcuts in WordPress (I'm using 3.2.1) the shortcut text doesn't output.
*UPDATE #2*
The problem looks like it's related to WordPress saving Drafts. Apparently with Lion and Safari 5.1 you can still work on the post page even though it's auto-saving a draft. Snow Leopard and Safari would just kind of lock-up when autosave occurs so you couldn't even type-in the shortcut. I'll report back if I see any other issues.
#4
Posted 29 July 2011 - 08:25 PM
Evan Gross, on 09 July 2011 - 09:31 PM, said:
Earlier versions of Spell Catcher X aren't totally compatible with Lion, as numerous changes were made to the way the Input menu works (for all input methods). These changes were (of course) dealt with in Spell Catcher X 10.4.
Spell Catcher is roaring with lion.
I did notice that if the program keyque was loaded at startup or login before Spell Cather, Spell Catcher for what ever reason did not load. When I reversed the order and made SpellCatcher first, SpellCatcher loaded up as expected, on startup.
I did notice that if you are using the TAB key, in the shorthand EXPANSION, that it causes the cursor to leave or jump out of some windows in the browser while working in Safari. You just have to use spaces instead of TAB. But otherwise SpellCatcher and its shorthand functions are working well so far.
Evan is there some way to load the shorthand menu without having a word highlighted and copied?
Sincerely,
William McCormick
#5
Posted 29 July 2011 - 10:39 PM
William McCormick, on 29 July 2011 - 08:25 PM, said:
I did notice that if the program keyque was loaded at startup or login before Spell Cather, Spell Catcher for what ever reason did not load. When I reversed the order and made SpellCatcher first, SpellCatcher loaded up as expected, on startup.
Is this 100% reproducible? What if you just remove Spell Catcher from your Login Items?
Quote
Can you give me a concrete example? Tabs in expansions are designed to behave exactly as if you typed them, so it sounds like it's all working as-designed. What is the exact problem you're seeing with this?
Quote
I don't "get" what you're asking here. What are you referring to as the "shorthand menu"? Again, give me a concrete example. Include steps to reproduce, and include screen shots if necessary. Expanding shorthands doesn't cause words to be highlighted or copied.
#6
Posted 03 August 2011 - 06:55 AM
You are absolutely right about the tab key in shorthand, SpellCatcher is working just fine. I thought that if someone was having trouble with a shorthand in a browser, that it could be the tab key used in a shorthand. I know it had me stumped for a while.
When you right click the Spell Catcher menu and look to modify the shorthand editor , the shorthand editor only opens if you have something copied in the clipboard. I just thought an open shorthand editor choice would be cool.
Sincerely,
William McCormick
#7
Posted 03 August 2011 - 07:41 PM
William McCormick, on 03 August 2011 - 06:55 AM, said:
William McCormick
#8
Posted 03 August 2011 - 09:01 PM
Evan Gross, on 03 August 2011 - 07:41 PM, said:
The spell catcher menu.
I go to the SpellCatcher menu and click the shorthand choice and I cannot open the editor unless, I have something in the clipboard.
Many times I just wish to add shorthands manually in the shorthand editor. To see which ones I have already.
Sincerely,
William McCormick
#9
Posted 03 August 2011 - 09:28 PM
William McCormick, on 03 August 2011 - 09:01 PM, said:
I go to the SpellCatcher menu and click the shorthand choice and I cannot open the editor unless, I have something in the clipboard.
Many times I just wish to add shorthands manually in the shorthand editor. To see which ones I have already.
Sincerely,
William McCormick
You mean the New Shorthand for Selection command?
Post a screenshot along with steps to reproduce.
#10
Posted 25 August 2011 - 08:57 PM
Thought you would like to be informed that I finally succeeded in having my Spell Catcher 10.4’s input method load in Apple OS 10.7.
Spell Catcher’s yellow arrow (64-bit) now appears in my Language and Text menu. The solution was simply a re-installation of Lion. Evidently, I encountered a problem with Apple’s download of Lion from Apple Store. My first download was not a complete download of the new operating system, a problem ultimately resolved by the re-installation via Apple’s Recovery Disk Assistant.
You may recall communicating with me (Julius Lee) intermittently via email regarding the input issue.
Julius Lee
#11
Posted 30 September 2011 - 07:00 AM
I am finding SC is far more unstable in Lion than before, causing crashes in Mail, and other programmes as well as the continuing problems with Scrivener.
Is there any obvious setting I should change/remove in SC?
I use SC all the time, so this is a real pain.
Look forward to hearing from you. Thanks and regards, Jack
#12
Posted 30 September 2011 - 12:49 PM
jackl73, on 30 September 2011 - 07:00 AM, said:
I am finding SC is far more unstable in Lion than before, causing crashes in Mail, and other programmes as well as the continuing problems with Scrivener.
Is there any obvious setting I should change/remove in SC?
I use SC all the time, so this is a real pain.
Look forward to hearing from you. Thanks and regards, Jack
When you say "than before," do you mean than Snow Leopard? Or do you mean you're seeing (new) problems on Lion itself?
Make sure that in Mail, Safari, and any other apps that use WebKit for editing text (I know, hard to tell at a glance, but there a few), make sure you disable (turn off, deselect) Check Spelling While Typing (in Edit > Spelling and Grammar…). In Mail you would generally set When to check spelling to "Never" in the Composing pane of Mail's Preferences window.
This avoids a known bug in WebKit's support for the Mac OS X system-wide spell checker. Shouldn't be a big deal, as you would be using Spell Catcher to check while typing anyway.
I've never been able to reproduce any of the problems that have been reported with Scrivener. Can you give me more details?
Also, tell me what the "other programmes as well" specifically are. Include versions, and steps to reproduce.
#13
Posted 03 October 2011 - 12:43 PM
jackl73, on 30 September 2011 - 07:00 AM, said:
I am finding SC is far more unstable in Lion than before, causing crashes in Mail, and other programmes as well as the continuing problems with Scrivener.
Is there any obvious setting I should change/remove in SC?
I use SC all the time, so this is a real pain.
Look forward to hearing from you. Thanks and regards, Jack
Euan,
I had Check Spelling while you type ticked in both Mail and Safari. that should improve things. I suspect they were changed somehow when I moved to Lion and so things just seemed worse generally.
Scrivener: I know you cannot replicate any of the problems, but for me and may Scrivener users they do exist. BUT just checked the Preferences in Scrivener and ..... Check Spelling while typing was ticked.
Hopefully that has solved ALL MY PROBLEMS.
Thanks as always for SC and your help. Regards, Jack
#14
Posted 09 October 2011 - 04:09 PM
Any suggestions? I’ve tried turning off spelling correction in Mail/Prefernces without change. Also note that correction in this message is variablle.
Thnx
Rich
#15
Posted 10 October 2011 - 04:11 PM
RichK, on 09 October 2011 - 04:09 PM, said:
Any suggestions? I’ve tried turning off spelling correction in Mail/Prefernces without change. Also note that correction in this message is variablle.
Thnx
Rich
Try using DirectCorrect, along with the "New Paragraphs and lines should always be considered to begin a sentence" preference (Spell Catcher Preferences, Spelling pane, Check Selection tab). It might work better for you.





