>
>On 11 Jul 2014, at 7:44 am, João Varela wrote:
>
>>Ithas been officially declared by Apple that cell-based NSOutlineView¹s
>>and
>>NSTableView's are deprecated.
>
>Would you care to point to where? I'm not arguing, but you wouldn't think
>so from the documentation. I see: "NSCell-based tables
In case anyone's following along, I followed Ken's suggestion and made a
subclass of NSTextField, and moved my
textView:willChangeSelectionFromCharacterRange:toCharacterRange: delegate
method there.
I also followed Bill's suggestion of overriding becomeFirstResponder so that I
could disallow
On Jul 11, 2014, at 2:54 AM, Quincey Morris
wrote:
> I guess you could solve it with a NSTextField subclass that overrides
> becoming first responder. Or is there a more direct solution, do you think?
Yes, that's exactly what I do, and it works. Override -[NSResponder
becomeFirstResponder].
On 11 Jul 2014, at 6:37 pm, Ken Thomases wrote:
> In general, an NSCell is owned by a control (instance of some subclass of
> NSControl). An NSCell uses the field editor, an instance of NSText or a
> subclass (usually an NSTextView or subclass, more specifically), to handle
> the actual editi
On Jul 11, 2014, at 2:24 AM, Shane Stanley wrote:
> FWIW, in my cell-based version I used
> textView:willChangeSelectionFromCharacterRange:toCharacterRange: in my
> outline view subclass. But that no longer seems to get called.
In general, an NSCell is owned by a control (instance of some subc
On 11 Jul 2014, at 5:44 pm, Quincey Morris
wrote:
> In such a case, it’s also worth re-considering your UI at a higher level.
>
> I wonder, for example, whether there’s an alternative that uses *two* text
> fields. Put the file name in the ‘textField’ outlet field, and put the
> extension in
On Jul 11, 2014, at 00:24 , Shane Stanley wrote:
> Just seems a lot of work for something that doesn't strike me as an uncommon
> need.
In such a case, it’s also worth re-considering your UI at a higher level.
I wonder, for example, whether there’s an alternative that uses *two* text
fields.
On 11 Jul 2014, at 5:24 pm, Shane Stanley wrote:
>> I guess you could solve it with a NSTextField subclass that overrides
>> becoming first responder.
>
> That's all I can think of.
Well not quite. I'm already overriding keyDown: in the outline view to show QL
previews, so it might be easier
On 11 Jul 2014, at 4:34 pm, Ken Thomases wrote:
> Have you connected the delegate outlet of your text view (field?)?
Yes.
On 11 Jul 2014, at 4:54 pm, Quincey Morris
wrote:
> 1. The delegate method ‘control:textShouldBeginEditing:’ seems like it’s
> called too late. Presumably the selection
On Jul 10, 2014, at 23:34 , Ken Thomases wrote:
> Have you connected the delegate outlet of your text view (field?)?
This was my first thought, too, but:
1. The delegate method ‘control:textShouldBeginEditing:’ seems like it’s called
too late. Presumably the selection change needs to be done w
On Jul 11, 2014, at 12:54 AM, Shane Stanley wrote:
> I'm still not quite out of the woods. In my cell-based outline view, when the
> user selects an item and hits return to edit it, I change the selection so
> that only the file name before the extension was selected. I do that with
> text vie
I'm still not quite out of the woods. In my cell-based outline view, when the
user selects an item and hits return to edit it, I change the selection so that
only the file name before the extension was selected. I do that with text view
delegate methods in my outline view subclass, but that does
On 11 Jul 2014, at 1:56 am, Quincey Morris
wrote:
> You are doing something basic incorrectly. That NSOutlineView delegate method
> is called ‘outlineView:viewForTableColumn:item:’.
Sigh. Thank you for restoring my faith in my own stupidity...
--
Shane Stanley
___
On Jul 10, 2014, at 00:25 , Shane Stanley wrote:
> I fear I'm doing something basic incorrectly, but I can't see what. My
> -outlineView:viewForTableColumn:row: is not even getting called, which seems
> very odd. (And yes, I commented out
> -outlineView:willDisplayCell:forTableColumn:item:). A
On Jul 10, 2014, at 2:25 AM, Shane Stanley wrote:
> I'm trying to convert a cell-based outline view to view-based. The model is a
> file wrapper, I'm using a datasource, and it was working fine while
> cell-based. I changed from a text cell to NSTableCellView, and when I set it
> up to use bin
On 10 Jul 2014, at 6:37 pm, Bill Cheeseman wrote:
> All I can say from my experience is that it requires a lot of trial-and-error
Thanks, Bill -- I was hoping someone would pipe up and say I forgot to do X. Oh
well...
On 10 Jul 2014, at 10:00 pm, Graham Cox wrote:
> Is there some good reason
On Jul 10, 2014, at 8:00 AM, Graham Cox wrote:
> Is there some good reason to change to view-based, or are you doing it just
> because it seems to be the "modern" thing? I'd say, if it ain't broke...
I know you addressed your question to Shane, but speaking for myself: I'm
writing a new appl
On 10 Jul 2014, at 5:25 pm, Shane Stanley wrote:
> I'm trying to convert a cell-based outline view to view-based.
Is there some good reason to change to view-based, or are you doing it just
because it seems to be the "modern" thing? I'd say, if it ain't broke...
I've recently gone through a
On Jul 10, 2014, at 3:25 AM, Shane Stanley wrote:
> I'm trying to convert a cell-based outline view to view-based. The model is a
> file wrapper, I'm using a datasource, and it was working fine while
> cell-based. I changed from a text cell to NSTableCellView, and when I set it
> up to use bi
19 matches
Mail list logo
