8 replies to this topic

[jbarse]

Hi, I just upgraded to 10.1 and there seems to be a conflict with Timbuktu 7.0. I'm running Mac OS X 10.3.2 on a Dual 1GHz G4 (Mirrored Drive Doors) with 1GB RAM.

If the Spell Catcher Input Method is active and I try to launch TB2, TB2 will "unexpectedly quit". If I change the Input Method to the US Keyboard TB2 will launch and behave properly. Likewise, if TB2 is already running and I change the Input Method from the US keyboard to Spell Catcher TB2 will also "unexpectedly quit."

I had no problems with TB2 7.0 and Spell Catcher 10.0.2...

I can send you the output of Apple's crash reporter if you like.

-- Jack

[Evan Gross]

jbarse, on Feb 10 2004, 05:06 PM, said:

Hi, I just upgraded to 10.1 and there seems to be a conflict with Timbuktu 7.0. I'm running Mac OS X 10.3.2 on a Dual 1GHz G4 (Mirrored Drive Doors) with 1GB RAM.

If the Spell Catcher Input Method is active and I try to launch TB2, TB2 will "unexpectedly quit". If I change the Input Method to the US Keyboard TB2 will launch and  behave properly. Likewise, if TB2 is already running and I change the Input Method from the US keyboard to Spell Catcher TB2 will also "unexpectedly quit."

I had no problems with TB2 7.0 and Spell Catcher 10.0.2...

I can send you the output of Apple's crash reporter if you like.

-- Jack

Email the crash report to our support at rainmakerinc dot com address.

We had a report of this, I installed Timbuktu, but couldn't reproduce it.

[jbarse]

Quote

Email the crash report to our support at rainmakerinc dot com address.

We had a report of this, I installed Timbuktu, but couldn't reproduce it.

Just sent it... please let me know if you need more info from me. Happy to help out in any way I can...

Jack

[Evan Gross]

jbarse, on Feb 10 2004, 07:26 PM, said:

Quote

Email the crash report to our support at rainmakerinc dot com address.

We had a report of this, I installed Timbuktu, but couldn't reproduce it.

Just sent it... please let me know if you need more info from me. Happy to help out in any way I can...

Jack

I don't have the email you sent yet - usually it only takes a couple of minutes.

Might have gotten spam filtered - try it again if you can.

[jbarse]

Evan Gross, on Feb 10 2004, 07:43 PM, said:

Quote

I don't have the email you sent yet - usually it only takes a couple of minutes.

Might have gotten spam filtered - try it again if you can.

My fault...sent it to the wrong place. Just resent...

[biosun]

I can confirm and reproduce this behavior. When Spell Catcher is chosen as the input method, Timbuktu immediately "unexpectedly quits" Running OS X 10.3.2 with Timbuktu 7.0

Makes no difference if I choose "Open Timbuktu" or "Timbuktu Info" from menubar or launch Timbuktu using application icon.

Please look into this, I need Timbuktu.

[Evan Gross]

biosun, on Feb 10 2004, 11:38 PM, said:

I can confirm and reproduce this behavior. When Spell Catcher is chosen as the input method, Timbuktu immediately "unexpectedly quits" Running OS X 10.3.2 with Timbuktu 7.0

Makes no difference if I choose "Open Timbuktu" or "Timbuktu Info" from menubar or launch Timbuktu using application icon.

Please look into this, I need Timbuktu.

We are absolutely looking into this. It will NOT be resolved within 24 hours of the release of a new product version! Hang in there.

I couldn't reproduce this the other day when I tried - but just took a look again and I can reproduce it.

As long as I can reproduce it, I can fix it - provided it is actually my bug (it appears to be, but with input methods, appearances can sometimes be deceiving).

[Evan Gross]

Evan Gross, on Feb 10 2004, 11:47 PM, said:

biosun, on Feb 10 2004, 11:38 PM, said:

I can confirm and reproduce this behavior. When Spell Catcher is chosen as the input method, Timbuktu immediately "unexpectedly quits" Running OS X 10.3.2 with Timbuktu 7.0

Makes no difference if I choose "Open Timbuktu" or "Timbuktu Info" from menubar or launch Timbuktu using application icon.

Please look into this, I need Timbuktu.

We are absolutely looking into this. It will NOT be resolved within 24 hours of the release of a new product version! Hang in there.

I couldn't reproduce this the other day when I tried - but just took a look again and I can reproduce it.

As long as I can reproduce it, I can fix it - provided it is actually my bug (it appears to be, but with input methods, appearances can sometimes be deceiving).

Ok, I lied. We might have a work-around for this one already.

Waiting for confirmation that it really works from a couple of folks, then we'll post something in our FAQs or here - not quite sure yet.

[paulc]

Actually, the word should be "misspoke."

Ah, now I see. You don't use legitimate words that aren't listed in SCX's references! It flags misspoke as misspelled!