8 replies to this topic

[braintoniq]

I'm running Spell Catcher 10.4 on a brand new MacBook Air 11" with Lion. I'm finding on long auto shorthands, that when using Mail or Safari and I trigger a shorthand
via one of my shortcuts, it stops about 2 paragraphs in and break the program (i.e., spinning ball and I need to force quit). Yet, if I run that same shortcut in something like TextEdit, it works just fine. I've repeated this over and over to test it, even restarted and used a variety of longer shortcuts. Always the same behavior (but perfectly well behaved in TextEdit).

My current fix is to keep TextEdit open, run the shortcut there, then copy/paste the text into the app I need it for.

Scott

[Evan Gross]

braintoniq, on 25 July 2011 - 10:51 PM, said:

I'm running Spell Catcher 10.4 on a brand new MacBook Air 11" with Lion. I'm finding on long auto shorthands, that when using Mail or Safari and I trigger a shorthand
via one of my shortcuts, it stops about 2 paragraphs in and break the program (i.e., spinning ball and I need to force quit). Yet, if I run that same shortcut in something like TextEdit, it works just fine. I've repeated this over and over to test it, even restarted and used a variety of longer shortcuts. Always the same behavior (but perfectly well behaved in TextEdit).

My current fix is to keep TextEdit open, run the shortcut there, then copy/paste the text into the app I need it for.

Scott

In Safari and/or Mail, do you have Edit > Spelling and Grammar > Check Spelling While Typing selected? Sounds like the same old WebKit bug from Snow Leopard.

Can you send the report you get when you Force Quit to our feedback address? Or if you don't get anything useful from Force Quit, take a sample with Activity Monitor when you get the beachball, save it as text, and email that. Should be easy for me to tell whether or not it's the same old WebKit bug or not...

[braintoniq]

Evan Gross, on 25 July 2011 - 11:00 PM, said:

In Safari and/or Mail, do you have Edit > Spelling and Grammar > Check Spelling While Typing selected? Sounds like the same old WebKit bug from Snow Leopard.

Can you send the report you get when you Force Quit to our feedback address? Or if you don't get anything useful from Force Quit, take a sample with Activity Monitor when you get the beachball, save it as text, and email that. Should be easy for me to tell whether or not it's the same old WebKit bug or not...

Awesome. That fixed the issue in both apps. I unchecked all of the spelling features in both, and now the shortcuts work again. Thank you. If you still would like the Activity monitor stuff, I can turn them back on to create the error and send you the text. I'd be glad to do that.

I do notice, too, that the shortcuts in Mail go 2 or 3 times as slow as if done in TextEdit or Safari. Probably because of Mail's formatting (vs. just straight text in the others).

thanks again for writing back so quickly.

Scott

[Evan Gross]

braintoniq, on 25 July 2011 - 11:09 PM, said:

Awesome. That fixed the issue in both apps. I unchecked all of the spelling features in both, and now the shortcuts work again. Thank you. If you still would like the Activity monitor stuff, I can turn them back on to create the error and send you the text. I'd be glad to do that.

I do notice, too, that the shortcuts in Mail go 2 or 3 times as slow as if done in TextEdit or Safari. Probably because of Mail's formatting (vs. just straight text in the others).

thanks again for writing back so quickly.

Scott

Since it sounds like you're seeing the same WebKit bug as was present in Snow Leopard (and that I reported to Apple some time ago), I don't need any logs or sample reports.

As for Mail's performance with shorthand expansions, there could be a couple of reasons for that. I'll take a look and see if there's anything I can do about it on my end.

Just tell me whether it matters if you are composing a Plain or Rich Text message…

[braintoniq]

Evan Gross, on 25 July 2011 - 11:21 PM, said:

Just tell me whether it matters if you are composing a Plain or Rich Text message…

In terms of speed, TextEdit's shortcut go fast whether it's Plain text or Rich. I've checked that out.

And because Mail can't yet accept Styled Text, it doesn't matter to me if use TextEdit in Rich or Plain (although I do have the default set to Plain). I do look forward to using that new Style Text feature once Mail allows it! It's going to help tremendously, especially on these long shortcuts (and I have quite a few of them, basically auto responses to common inquiries for our business). We use them all day long.

Scott

[Evan Gross]

braintoniq, on 25 July 2011 - 11:46 PM, said:

In terms of speed, TextEdit's shortcut go fast whether it's Plain text or Rich. I've checked that out.

And because Mail can't yet accept Styled Text, it doesn't matter to me if use TextEdit in Rich or Plain (although I do have the default set to Plain). I do look forward to using that new Style Text feature once Mail allows it! It's going to help tremendously, especially on these long shortcuts (and I have quite a few of them, basically auto responses to common inquiries for our business). We use them all day long.

Scott

I'm not referring to whether a shorthand expansion is plain or styled, but whether the email you're composing is plain or rich text. So Mail can certainly create both plain and styled messages - I just wanted to know which you were composing when you noticed the performance issue. And whether it made any difference if you were composing a plain or rich text email message.

[braintoniq]

Got it, thanks for the clarity.

Ok, I did some testing: In Mail, I normally always have prefs set to compose emails in Rich text. I accept Rich text and always send out in Rich Text.

When I go back and switch Mail's spelling features back ON, with Rich Text on, trying to type a Shorthand expansion crashes the app after about 500-700 characters, as mentioned above. If I switch to Plain text while spelling features are on, the Shorthand expansion works just fine.

Of course, if I switch to Plain text, the shorthand expansions work whether spelling features are on or off.

Hope that helps.

[Evan Gross]

braintoniq, on 26 July 2011 - 11:04 AM, said:

Got it, thanks for the clarity.

Ok, I did some testing: In Mail, I normally always have prefs set to compose emails in Rich text. I accept Rich text and always send out in Rich Text.

When I go back and switch Mail's spelling features back ON, with Rich Text on, trying to type a Shorthand expansion crashes the app after about 500-700 characters, as mentioned above. If I switch to Plain text while spelling features are on, the Shorthand expansion works just fine.

Of course, if I switch to Plain text, the shorthand expansions work whether spelling features are on or off.

Hope that helps.

This isn't really what I asked - I know that in Mail, if Check Spelling While Typing is selected, shorthands can trigger a WebKit bug that causes a hang.

I just wanted to know whether the performance expansions was different when composing Plain Text vs. Rich Text messages. I did some of my own testing and it doesn't seem to matter.

Why the performance of longer expansions is poor in Mail is a bit of a mystery. I haven't had time to really look at it yet.

[braintoniq]

Evan Gross, on 27 July 2011 - 01:42 AM, said:

Why the performance of longer expansions is poor in Mail is a bit of a mystery. I haven't had time to really look at it yet.

I checked that, too. No difference in shorthand expansions with Rich or Plain text in Mail (or TextEdit).