Can’t keep 10.3.3 active
#1
Posted 18 January 2010 - 07:16 AM
The problem is that the input method doesn’t stay selected. It will go for stretches where it does, then it will turn back to the flag and I have to reset it again.
Do I still need to run the Activator?
Is there something else I haven’t done? I haven’t set Mail and Safari back to 64 bit yet, just wanted to see how this works, but I'm presuming that I should be able to do so.
Would appreciate any advice on getting the input method to stay selected.
And FYI, I had this problem with 10.3.2 as well, even after following Evan’s instructions and changing these apps to 32 bit under Snow Leopard. I’d run Activator, the input method would sometimes stay on, then sometimes revert back to the flag. Very rarely had this issue prior to Snow Leopard.
#2
Posted 19 January 2010 - 02:05 AM
rmathes, on Jan 18 2010, 07:16 AM, said:
The problem is that the input method doesn’t stay selected. It will go for stretches where it does, then it will turn back to the flag and I have to reset it again.
Do I still need to run the Activator?
Is there something else I haven’t done? I haven’t set Mail and Safari back to 64 bit yet, just wanted to see how this works, but I'm presuming that I should be able to do so.
Would appreciate any advice on getting the input method to stay selected.
And FYI, I had this problem with 10.3.2 as well, even after following Evan’s instructions and changing these apps to 32 bit under Snow Leopard. I’d run Activator, the input method would sometimes stay on, then sometimes revert back to the flag. Very rarely had this issue prior to Snow Leopard.
No, the Activator is not needed, and won't do anything anyway if the version of Spell Catcher that's running isn't 10.3.2. Feel free to trash it.
Check the following:
1. In Language & Text System Preferences, Input Sources tab, make sure that your input source options are set to "Use the same one in all documents".
2. In the list of input sources, make sure that Spell Catcher’s input method application (yellow checkmark with the little "64" badge is turned "On". There's generally no need to have the input method component (plain yellow checkmark) turned on. So if it's "On" as well, turn it off.
Realize that the Mac OS will forcibly select a keyboard at certain times - generally when you have to enter an admin password in an authentication dialog. It should automatically re-select the previously active input source once the auth dialog closes, though.
You may also want to check the keyboard shortcuts that are assigned to switch input sources. If they are set to shortcuts you may accidentally type, think about changing them. Disable them entirely if you wish, but they can be very useful.
Let me know your experiences and results, I should probably create a FAQ for this as a few folks are writing in with the same basic question.
#3
Posted 19 January 2010 - 07:35 AM
Also, in the input list for SC I have 3 options to check or not check: SC, SC Cyrillic, and SC Unicode. The first and last are checked. Not sure what the Unicode option is. Does that need to be checked?
#4
Posted 19 January 2010 - 07:42 AM
rmathes, on Jan 19 2010, 07:35 AM, said:
Also, in the input list for SC I have 3 options to check or not check: SC, SC Cyrillic, and SC Unicode. The first and last are checked. Not sure what the Unicode option is. Does that need to be checked?
I posted a new FAQ on the topic.
If you use a Unicode keyboard like U.S. Extended, you might want to use Spell Catcher Unicode input mode. If not, you can turn it off.
Not sure why it's getting turned on for some folks, might simply be that all keyboards on Snow Leopard are Unicode-savvy, though it's a bit of a mystery why Spell Catcher is classifying some that don't generate Unicodes outside of the standard Roman range are being classified that way. Seems that the behavior of these APIs (deprecated on Snow Leopard, but should still work the same as on previous versions of Mac OS X) to classify a keyboard has changed since I started working on Snow Leopard.
Yet another thing to look into.
#5
Posted 19 January 2010 - 09:58 AM
Evan Gross, on Jan 19 2010, 12:05 AM, said:
1. In Language & Text System Preferences, Input Sources tab, make sure that your input source options are set to "Use the same one in all documents".
FYI, even though I have not experienced any problems since installing 10.3.3, I wanted to let you know that my option to "Use the same input for all documents" was not set either. I believe we were told to manually check this when we were using the Activator for the prior version. This tells me that the installation does not (always) change it to the above setting, and we are not instructed to manually do this in any of the installation instructions of 10.3.3. So if it is important and can cause an issue, we should at least be told do this during the installation process.
Also, my SCX Unicode option was also checked, like I said, I have not experienced any issues (but I am a relatively lite-straight forward user), but I can confirm I had two out of the three input option of SCX checked as well.
For what its worth,
Tom
Aluminum Powerbook 13"
Snow Leopard 10.6.2
#6
Posted 19 January 2010 - 10:03 AM
How would I know if I'm using a Unicode extended keyboard? I have no idea what that means.
I’m using the wired Apple aluminum thin keyboard that has function keys up top and a separate numeric keypad to the side.
#7
Posted 19 January 2010 - 11:22 AM
rmathes, on Jan 19 2010, 10:03 AM, said:
How would I know if I'm using a Unicode extended keyboard? I have no idea what that means.
I’m using the wired Apple aluminum thin keyboard that has function keys up top and a separate numeric keypad to the side.
When I say "Keyboard", usually I'm talking about input sources..
In the Finder, choose Help > Mac Help, search for "input source", "Input menu", "input method" and read all about it.
#8
Posted 27 January 2010 - 02:01 AM
#9
Posted 27 January 2010 - 06:50 AM
kitmosden, on Jan 27 2010, 02:01 AM, said:
Please don't use Spell Catcher X 10.3.2 on Snow Leopard. Update to 10.3.4, it's free, and works much better on 10.6.
Then read this FAQ.
#10
Posted 27 January 2010 - 06:59 AM
#11
Posted 27 January 2010 - 12:19 PM
Evan Gross, on Jan 27 2010, 06:50 AM, said:
Then read this FAQ.
Hi Evan,
I am using 10.3.4 but have 2 copies is of SC in the Language & Text System Preferences, Input Sources.
Cheers,
Kit
#12
Posted 27 January 2010 - 12:27 PM
kitmosden, on Jan 27 2010, 12:19 PM, said:
I am using 10.3.4 but have 2 copies is of SC in the Language & Text System Preferences, Input Sources.
Cheers,
Kit
If that's what you see, generally you'll have the input method application turned "On", and the input method component Off.
If that's not what you see, post a screenshot.
#13
Posted 04 February 2010 - 02:20 AM
Evan Gross, on Jan 27 2010, 06:50 AM, said:
Then read this FAQ.
Hi Evan,
I've tried everything mentioned here but still can't keep 10.3.4 active. I have even had SC deselect itself (in menu bar) in the middle of a sentence.
#14
Posted 04 February 2010 - 09:47 PM
kitmosden, on Feb 4 2010, 02:20 AM, said:
I've tried everything mentioned here but still can't keep 10.3.4 active. I have even had SC deselect itself (in menu bar) in the middle of a sentence.
#15
Posted 05 February 2010 - 01:01 AM
Evan Gross, on Feb 4 2010, 10:47 PM, said:
No but I suppose it’s possible I have a conflicting keyboard command somewhere. I’ll have to look for that.
Thanks,
Kit
#16
Posted 05 February 2010 - 11:35 AM
kitmosden, on Feb 4 2010, 02:20 AM, said:
I've tried everything mentioned here but still can't keep 10.3.4 active. I have even had SC deselect itself (in menu bar) in the middle of a sentence.
I just updated to 10.3.4 and I can't keep SC active. I have read the FAQ and checked through everything mentioned. My macbook is not 64 bit enabled. SC goes inactive whenever I shift to the Finder, AND the SC option in the menubar goes blank/gray when in Finder mode (it can't be selected.) If I only shift through applications, SC will stay active.
Also, the input source keyboard shortcuts (e.g. command-space) seem to be the system default for spotlight (and I do not have them active for spell checker.)
Dennis
#17
Posted 05 February 2010 - 12:11 PM
#18
Posted 05 February 2010 - 12:20 PM
Dennis
#19
Posted 05 February 2010 - 03:36 PM
kitmosden, on Feb 5 2010, 02:01 AM, said:
Thanks,
Kit
The conflict appears to be LaunchBar which uses Command Spacebar but I can’t see, offhand, what the conflict is with SpellCatcher????
And no I don’t use Command Spacebar for Spotlight.
#20
Posted 05 February 2010 - 04:35 PM
kitmosden, on Feb 5 2010, 03:36 PM, said:
And no I don’t use Command Spacebar for Spotlight.
This is a Mac OS X shortcut - nothing to do with Spell Catcher in particular.






