On Aug 18, 2009, at 5:15 AM, Graham Cox wrote:
On 18/08/2009, at 9:50 PM, Graham Cox wrote:
Here's a fun little method I wrote to explore this - it just fakes
an event that gradually tracks from the top of the table to the
bottom. As you can see, you wouldn't really expect it to draw
an
On Aug 17, 2009, at 7:22 PM, Adam R. Maxwell wrote:
On Aug 17, 2009, at 11:54 AM, Quincey Morris wrote:
On Aug 17, 2009, at 11:14, I. Savant wrote:
I'm not sure what you mean here, but I'm fairly sure I disagree. :-D
This is one step in the right direction. One. At least, insofar as
"we
Hi Corbin, thanks for the clarification. I didn't re-read the
release notes when looking for information on this I must admit,
though the exact wording doesn't immediately clarify the precise
issue. But I do understand the thinking a little better now. This
though:
If no menu was retu
On 18/08/2009, at 9:50 PM, Graham Cox wrote:
Here's a fun little method I wrote to explore this - it just fakes
an event that gradually tracks from the top of the table to the
bottom. As you can see, you wouldn't really expect it to draw
anything, but it does highlight each row in turn. Th
On 18/08/2009, at 9:07 PM, I. Savant wrote:
It's not quite the same because a menu is another view and the
table view is merely holding a reference to it. This is more an
encapsulation problem.
Sorry for being so quick to "play the MVC card". ;-)
In a way though, I think you're right.
On Aug 18, 2009, at 6:54 AM, I. Savant wrote:
It's akin to asking the AddressBook person view for its "-lastName"
field contents and having it highlight the field before giving up
its secrets. MVC? Feh! We don't need no MVC! ;-)
Sorry, let me explain my thoughts a bit more here. I'm not
On Aug 17, 2009, at 10:32 PM, Graham Cox wrote:
It seems strange because on the face of it -menuForEvent: is meant,
as far as I can see, merely to return a property - the view's
contextual menu (the event providing the context). What is done with
the menu as far as displaying it, is down to
On 18/08/2009, at 2:27 AM, Corbin Dunn wrote:
It seems strange to me that this method is doing highlighting duty
when all it's meant for is to return a property.
To me, it doesn't seem strange. It is AppKit that displays the menu,
and it allows a consistent user interface to be used throug
On Aug 17, 2009, at 11:54 AM, Quincey Morris wrote:
On Aug 17, 2009, at 11:14, I. Savant wrote:
I'm not sure what you mean here, but I'm fairly sure I disagree. :-D
This is one step in the right direction. One. At least, insofar as
"we heard a very common request and, in the interests of
On 18/08/2009, at 2:27 AM, Corbin Dunn wrote:
Copied below is the pertinent information:
NSTableView/NSOutlineView - Contextual menu support
NSTableView and NSOutlineView now have better contextual menu
support. Please see the DragNDropOutlineView demo application for
an example of how t
On Aug 17, 2009, at 11:14, I. Savant wrote:
I'm not sure what you mean here, but I'm fairly sure I disagree. :-D
This is one step in the right direction. One. At least, insofar as
"we heard a very common request and, in the interests of consistency
and promoting good-looking apps on our p
On Aug 17, 2009, at 1:48 PM, Quincey Morris wrote:
My guess is that I. S. wasn't referring to specific defects (though
there are those) but to the "Frankenstein's monster" nature of
NSTableView/NSOutlineView -- a lot of not-quite-matching pieces
bolted onto the corpse of a much simpler clas
--
I.S.
On Aug 17, 2009, at 12:30 PM, Corbin Dunn wrote:
Hopefully customization has become easier, and frequently less
required (ie: the "source list" highlighting style, proper drag and
drop feedback, etc). Do you have specific examples of things that
are difficult to do which should
On Aug 17, 2009, at 09:30, Corbin Dunn wrote:
Hopefully customization has become easier, and frequently less
required (ie: the "source list" highlighting style, proper drag and
drop feedback, etc). Do you have specific examples of things that
are difficult to do which should be easier? I'm
On Aug 17, 2009, at 6:24 AM, I. Savant wrote:
On Aug 17, 2009, at 7:49 AM, Graham Cox wrote:
This indicates that the NSOutlineView's implementation of this
highlight is being done in a dubiously skanky way
Unfortunately this can describe numerous parts of NSTableView &
NSOutlineView. No
...then I get the highlight back again! This indicates that the
NSOutlineView's implementation of this highlight is being done in a
dubiously skanky way, drawing directly as part of the -menuForEvent:
method, rather than flagging the menu tracking and drawing as part
of the standard draw
On Aug 17, 2009, at 7:49 AM, Graham Cox wrote:
This indicates that the NSOutlineView's implementation of this
highlight is being done in a dubiously skanky way
Unfortunately this can describe numerous parts of NSTableView &
NSOutlineView. Not a knock against the engineers, but this is one
On 17/08/2009, at 10:21 AM, Graham Cox wrote:
I have an outline view using source list style.
When I right-click on the view, the item under the mouse highlights
with a blue outline independent of the current selection. This gives
the impression that the menu command applies to that item,
On 2009 Aug 16, at 17:21, Graham Cox wrote:
I have an outline view using source list style.
When I right-click on the view, the item under the mouse highlights
with a blue outline independent of the current selection. This gives
the impression that the menu command applies to that item, no
I have an outline view using source list style.
When I right-click on the view, the item under the mouse highlights
with a blue outline independent of the current selection. This gives
the impression that the menu command applies to that item, not the
real selected item. In my case my menu
20 matches
Mail list logo