I just installed Spell Catcher X 10.4 for Mac. System OS 10.6.6.
Getting strange behavior in QuarkXPress 8.5 and 9 when I select a word. When I go to Check Word or Check Selection or Look Up, Spell Catcher shows the selected word and parts of other selections. Really hard to describe.
In Mac OS 10.5.8 everything works normal.
Strange Behavior
Started by William Bragg, Jun 08 2011 10:23 PM
6 replies to this topic
#1
Posted 08 June 2011 - 10:23 PM
#2
Posted 09 June 2011 - 02:37 PM
William Bragg, on 08 June 2011 - 10:23 PM, said:
I just installed Spell Catcher X 10.4 for Mac. System OS 10.6.6.
Getting strange behavior in QuarkXPress 8.5 and 9 when I select a word. When I go to Check Word or Check Selection or Look Up, Spell Catcher shows the selected word and parts of other selections. Really hard to describe.
In Mac OS 10.5.8 everything works normal.
Getting strange behavior in QuarkXPress 8.5 and 9 when I select a word. When I go to Check Word or Check Selection or Look Up, Spell Catcher shows the selected word and parts of other selections. Really hard to describe.
In Mac OS 10.5.8 everything works normal.
As well, tell me if this is new in Spell Catcher X 10.4, or also happened with earlier versions.
#3
Posted 11 June 2011 - 12:48 PM
Evan Gross, on 09 June 2011 - 02:37 PM, said:
If it's hard to describe, then take screenshots and either upload them here, or email them to our feedback address. I don't own QuarkXPress (any version) and am totally unfamiliar with how to use it. So do your best to describe and illustrate the problem.
As well, tell me if this is new in Spell Catcher X 10.4, or also happened with earlier versions.
As well, tell me if this is new in Spell Catcher X 10.4, or also happened with earlier versions.
QuarkXPress 8 and 9 have keystrokes to select various tools. ("T" for the Text Tool.) When I type "T" to select the text tool and then type a word like "from," Spell Catcher says curious because it shows the word as a Questionable Spelling and shows it as "Tfrom."
Spell Catcher is picking up the keystroke to select a tool. The solution seems to be to manually select the various tools and not use the QuarkXPress keystrokes.
#4
Posted 11 June 2011 - 09:12 PM
William Bragg, on 11 June 2011 - 12:48 PM, said:
Actually, my problem may not be a Spell Catcher problem, after all.
QuarkXPress 8 and 9 have keystrokes to select various tools. ("T" for the Text Tool.) When I type "T" to select the text tool and then type a word like "from," Spell Catcher says curious because it shows the word as a Questionable Spelling and shows it as "Tfrom."
Spell Catcher is picking up the keystroke to select a tool. The solution seems to be to manually select the various tools and not use the QuarkXPress keystrokes.
QuarkXPress 8 and 9 have keystrokes to select various tools. ("T" for the Text Tool.) When I type "T" to select the text tool and then type a word like "from," Spell Catcher says curious because it shows the word as a Questionable Spelling and shows it as "Tfrom."
Spell Catcher is picking up the keystroke to select a tool. The solution seems to be to manually select the various tools and not use the QuarkXPress keystrokes.
#5
Posted 12 June 2011 - 12:27 PM
Evan Gross, on 11 June 2011 - 09:12 PM, said:
The best solution is to set Spell Catcher X to use different keyboard shortcuts (in Quark, at least) that don't conflict.
#6
Posted 13 June 2011 - 12:07 PM
William Bragg, on 12 June 2011 - 12:27 PM, said:
The problem is not with Spell Catcher X keyboard shortcuts. It's with the QuarkXPress keyboard shortcuts which I can't change. When I type a QuarkXPress keyboard shortcut to select the Type Tool ("T") in order to start typing some text, Spell Catcher thinks that I'm typing "T" as the first letter of a word. And of course Spell Catcher then announces "Curious."
#7
Posted 13 June 2011 - 12:50 PM
Evan Gross, on 13 June 2011 - 12:07 PM, said:
Wait - are the QXP shortucts keys with no modifiers? In other words, they don't require the use of command, control or fn? Yep, that would be a problem if QXP isn't handling them such that they don't get forwarded to input methods…





