Re: Apple's Code Level Support
Re: Apple's Code Level Support
- Subject: Re: Apple's Code Level Support
- From: Ryan Stevens <email@hidden>
- Date: Mon, 28 Mar 2005 17:21:08 -0800
On Mar 28, 2005, at 11:02 AM, Max Seelemann wrote:
I've customized this textview and added a custom TextStorage and a custom LayoutManager. The TextStorage *should* work as a normal one, but in fact, it adds some counting functionality and does some customization to the attributesAtIndex: function of NSTextStorage. (But I don't think that this should be the problem). I call - (void)edited:(unsigned)editedMask range:(NSRange)range changeInLength:(int)delta; every time I do a change and everything works fine except of this drawing issue.
We can assume you're calling beginEditing and endEditing as well as (or in place of) edited:range:changeInLength:, right?
Why should I be doing so? These methodes just deal with interface update but my internal storage textStorage has no interface to update. So this would be some kind of waste of computing power. I'm just doing the necessary calls described in Apple's "How to override a NSTextStorage" documentation. This should be enough, shouldn't it?
*shrug*
Can't hurt to try can it? Beats sitting around waiting for Apple I'd think.
I probably should've asked whether or not you tried calling begin/endEditing instead of implying that you need to because I don't really know that you do (or if it's appropriate). I've never needed to subclass NSTextStorage, it was just the first thing that came to me and since you haven't said what you've already tried I figured wth.
A shot in the dark is better than no shot.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden