On Wed, Aug 3, 2011 at 3:32 PM, Aki Inoue a...@apple.com wrote:
Another approach is to use multiple field editor objects so that you keep the
first editor content unmodified.
That's not really an option in this situation. Our users' documents
often consist of thousands of rich text cells.
Kyle,
It appears you're right.
Another approach is to use multiple field editor objects so that you keep the
first editor content unmodified.
Aki
On 2011/08/02, at 18:37, Kyle Sluder wrote:
On Tue, Aug 2, 2011 at 6:09 PM, Aki Inoue a...@apple.com wrote:
Hi Tom,
Definitely write a Radar.
Hello, fellow cocoa devs.
I'm running down the most common crasher we're seeing in OmniPlan-2.0 under
Lion and running onto some grief with NSSpellChecker/NSTextView. We have a
fairly complex outline view that is backed by many text storages and the field
editor is asked to do a lot. When
Hi Tom,
Definitely write a Radar.
One thing you could try is overriding both -checkTextInRange:types:options:
-handleTextCheckingResults:forRange:types:options:orthography:wordCount: for
your field editor.
You can have some kind of the field editor session ID.
Every time a new field editor
On Tue, Aug 2, 2011 at 6:09 PM, Aki Inoue a...@apple.com wrote:
Hi Tom,
Definitely write a Radar.
I just got this distilled down into an extremely simple demo project.
rdar://problem/9886471
The demo project is here for any interested third parties: http://db.tt/7hA7i8m
One thing you could
