On Feb 7, 2013, at 23:15 , Kyle Sluder wrote:
> Subclass NSOutlineView and override -textDidEndEditing: to do the right
> thing? (Or whatever the delegate method is that gives you the "movement
> reason.")
Weirdly, it doesn't get to this delegate method -- nor does *my* delegate ever
get mess
On Feb 7, 2013, at 9:41 PM, Quincey Morris
wrote:
> Anyway, this gave me a simple test project, now bug-reported as #13178419.
> Unfortunately, I don't see a workaround.
Subclass NSOutlineView and override -textDidEndEditing: to do the right thing?
(Or whatever the delegate method is that giv
On Feb 7, 2013, at 16:00 , Quincey Morris
wrote:
> Everything works, except for one thing. If I click on a text field to begin
> editing, type a few characters, then press Esc, then editing ends, but the
> text doesn't revert to what it was before editing began.
Well, it appears to a NSOutlin
I'm stuck trying to understand a piece of NSOutlineView behavior. Perhaps I'm
just missing the obvious solution, but I can't see it.
I have an view-based outline view configured as a source list. The list itself
uses a data source, not bindings. The table cell view is a subclass of
NSTableCellV
