Closed akac closed 9 years ago
I can reproduce this in Pocket Informant, but not in the Note field of a task in OmniFocus. The next logical step would be to see if you can reproduce this in the demo app or another app with TextExpander touch support. Also, I cannot reproduce this when the Comment is in Rich Text mode in Pocket Informant.
Yep. I will try in the morning. For plaintext we use a UITextView but for rich text we use a webview.
We init the UITextView in a nib and don't use the delegates or any other calls except for TE and to save the text.
But I will see if I can get more info for you in the morning.
Alex Kac CEO/Founder Transcribed by Siri
On Dec 3, 2014, at 8:34 PM, gscown notifications@github.com wrote:
I can reproduce this in Pocket Informant, but not in the Note field of a task in OmniFocus. The next logical step would be to see if you can reproduce this in the demo app or another app with TextExpander touch support. Also, I cannot reproduce this when the Comment is in Rich Text mode in Pocket Informant.
— Reply to this email directly or view it on GitHub.
I’m also told the same thing happens in the ToDo app. I’m about to test in a moment.
On Dec 3, 2014, at 8:34 PM, gscown notifications@github.com wrote:
I can reproduce this in Pocket Informant, but not in the Note field of a task in OmniFocus. The next logical step would be to see if you can reproduce this in the demo app or another app with TextExpander touch support. Also, I cannot reproduce this when the Comment is in Rich Text mode in Pocket Informant.
— Reply to this email directly or view it on GitHub https://github.com/SmileSoftware/TextExpanderTouchSDK/issues/13#issuecomment-65533068.
Alex Kac - President and Founder Web Information Solutions, Inc.
"In the Country of the Blind, the one-eyed man is king." --Desiderius Erasmus
The key to reproducing this problem is to set nextDelegate to nil. It's not nil in the SDK, so we didn't see this problem in action. I found it when chasing a different, but related, issue.
We'll run the release candidate of the 3.0.5 SDK by some folks before posting it to GitHub and asking the CocoaPods maintainer to update. In the meantime, I encourage you to try the release candidate:
http://smilesoftware.com/downloads/test/teTouchSDK_3.0.5.zip
If it resolves your problem and works for you, I don't see any trouble in shipping with it if you'd rather not wait for the GitHub posting.
Aha, that makes sense. This is a view where we don’t have any need for the delegate calls, so that works :)
On Dec 8, 2014, at 12:11 PM, gscown notifications@github.com wrote:
The key to reproducing this problem is to set nextDelegate to nil. It's not nil in the SDK, so we didn't see this problem in action. I found it when chasing a different, but related, issue.
We'll run the release candidate of the 3.0.5 SDK by some folks before posting it to GitHub and asking the CocoaPods maintainer to update. In the meantime, I encourage you to try the release candidate:
http://smilesoftware.com/downloads/test/teTouchSDK_3.0.5.zip http://smilesoftware.com/downloads/test/teTouchSDK_3.0.5.zip If it resolves your problem and works for you, I don't see any trouble in shipping with it if you'd rather not wait for the GitHub posting.
— Reply to this email directly or view it on GitHub https://github.com/SmileSoftware/TextExpanderTouchSDK/issues/13#issuecomment-66168494.
Alex Kac - President and Founder Web Information Solutions, Inc.
"If at first you don't succeed, skydiving is not for you." -- Francis Roberts
I haven't tested this as its evening and I'm home, but I got this report from a customer:
"- Create a new event.
I've replicated this on an iPhone 5, iPhone 6, iPad 4 and iPad Air 2, running the latest versions of iOS, PI, and TE, and the stock keyboard.
Anyone else see this? "
We're using a UITextView with pretty much no customization at all in this area.