when I resize the window and need to adjust the frames of both
scroll views, calling -[NSTextView setFrame:] results in the
layout manager invalidating and ensuring layout for the newly
visible character range.
Why not just turn off text view width/height tracking for the
container during the resize? That should let the layout manager use
the existing layout information (ie: for the stale container size).
Because that's just moving the problem further down the line. When I
finally update the text container size for the first text view it
will begin to layout before I've reached the next line of my code
where I can fix the size of the second view.
My next suggestion would be to subclass NSLayoutManager and override
methods that handle invalidation, eg:
- (void) textContainerChangedGeometry:(NSTextContainer*)tc ;
- (void) invalidateLayoutForCharacterRange:(NSRange)charRng isSoft:
(BOOL)isSoft actualCharacterRange:(NSRange*)charRngPtr ;
- (void) invalidateLayoutForCharacterRange:(NSRange)charRng
actualCharacterRange:(NSRange*)charRngPtr ;
When your resize starts, set some flag on your subclass that makes all
those methods no-ops. When you've finished resizing both text systems,
clear your flag and re-invalidate as necessary.
But really, I might ask you why your own code is so delicate that it
needs both layout systems to be in some perfectly matched state at all
times. Surely your code could have a flag that tells it layout is not
yet synced up, and ancillary tasks should be avoided/delayed until a
stable state is established.
The other "state change" you explicitly touch upon is editing the
text. If you bracket all your changes to the text storage with
begin/end editing calls, you shouldn't trigger layout until all
your changes are finished (unless you're also inadvertently
triggering layout in other ways).
I'll see how that fits in with setting the 2 strings that are
dependent on each other. It may be a nice workaround.
Just be careful that you don't trigger layout while the text storage
has an edit open, eg:
[textStorage beginEditing];
[textStorage deleteCharactersInRange:someRange];
[layoutManager ensureLayoutForCharacterRange:NSMakeRange(0,
[textStorage length])];
[textStorage endEditing];
The layout system isn't tolerant of that. It used to just throw out-of-
bounds exceptions, though now it seems to give you exceptions with
nice explanations of what you've done wrong.
~Martin
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
