It’s been working pretty well since Snow Leopard. Haven’t had any weird undo
issues in a while.
> On Aug 23, 2015, at 4:56 PM, Jerry Krinock wrote:
>
> A long time ago, I was advised to use an old-fashioned data source on my
> outline views for Core Data trees, because NSTreeController did not
> On 24 Aug 2015, at 06:42, Ken Thomases wrote:
>
> For what it's worth, another standard behavior is Option-up
Ah, the secrets of the option key. 12 years a mac user and they just keep on
giving.
Thanks!
___
Cocoa-dev mailing list (Cocoa-dev@l
On Aug 23, 2015, at 5:56 PM, Seth Willits wrote:
>> On Aug 23, 2015, at 1:05 AM, sqwarqDev wrote:
>>
>> When the user navigates to the last item in the list, further presses on the
>> down arrow key do nothing, and the user has to reverse direction using the
>> up arrow. If the user is at the
> On Aug 23, 2015, at 1:05 AM, sqwarqDev wrote:
>
> When the user navigates to the last item in the list, further presses on the
> down arrow key do nothing, and the user has to reverse direction using the up
> arrow. If the user is at the first item and wants to choice the last, or vice
> ver
A long time ago, I was advised to use an old-fashioned data source on my
outline views for Core Data trees, because NSTreeController did not work the
way it should have.
Have those issues now been resolved now? I’m working on a new app, with Core
Data and Cocoa Bindings. The new app will requ
I have an NSPopupButton in my app with half a dozen or more menu item choices.
When a user clicks on the button, they can navigate up and down the menu items
by using the up and down arrow keys.
When the user navigates to the last item in the list, further presses on the
down arrow key do noth
