• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSTableView selectionShouldChangeInTableView: bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSTableView selectionShouldChangeInTableView: bug?


  • Subject: Re: NSTableView selectionShouldChangeInTableView: bug?
  • From: "Jaime Rios" <email@hidden>
  • Date: Wed, 2 Apr 2008 14:33:17 -0400

Hi,
This is an old message and I'm disappointed to see that no one has replied
to it. I'm working on a bug that only appears in Mac OS 10.3.x whereby my
NSTableView does not receive the tableViewSelectionDidChange message until I
click the Window.
The chain of events that cause this problem is as follows:

1 - User clicks on a row; controls on main window are modified to display
settings associated with row selection
2 - User clicks on another row; application displays a NSAlert dialog box
asking if they would like to save their changes
3 - User clicks either yes or no and NSTableView does not receive
the tableViewSelectionDidChange message

This problem does not happen in 10.4 or 10.5.

I've tried so many different recommendations, but I have't found anything
that works.

I'm contemplating whether or not I should simulate a keystroke to the window
to force the tableViewSelectionDidChange message to get to the NSTableView.

--
-Jaime

On Tue, Jul 10, 2007 at 1:31 PM, David Peredo <email@hidden>
wrote:

> I'm having a problem with the delegate for my NSTableView getting the
> selectionShouldChangeInTableView: method called twice when you return NO.
> This doesn't happen when YES is returned.
>
> for example, the following would print twice per click on the table:
> - (BOOL)selectionShouldChangeInTableView:(NSTableView *)aTableView {
>        NSLog(@"foo");
>        return NO;
> }
>
> I can't think of any reason why this behavior would be desirable. I also
> noticed that other people were experiencing the same problem (
> http://www.cocoadev.com/index.pl?SheetProblemsWithNSTableView). Anyone
> have a fix or work around? or is this, dare I say it, a Cocoa bug?
>
> Appreciate any help =)
> Dave
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> 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:
>
> This email sent to email@hidden
>



--
-Jaime
http://www.jaimerios.com
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Prev by Date: Can't add new file extension to app's document types
  • Next by Date: Re: Problem with Grouping the rotated object.
  • Previous by thread: Re: Can't add new file extension to app's document types
  • Next by thread: Re: CAOpenGLLayer
  • Index(es):
    • Date
    • Thread