• 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: I can't step into any message of Objective-C object
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I can't step into any message of Objective-C object


  • Subject: Re: I can't step into any message of Objective-C object
  • From: Jean-Daniel Dupas <email@hidden>
  • Date: Sun, 30 Mar 2008 14:17:11 +0200

When you use binding, Cocoa will "replace*" your observed object by a proxy object. This proxy object is responsible to trigger "change notifications" when you change an observed value.
This is probably what prevent gdb to "step into".


If you want to write a custom accessor that behave the same than you normal accessor, you have to do something like this:

- (void)setNewValue:(int)number {
  [self willChangeValueForKey:@"value"];
  m_value = value;
  [self didChangeValueForKey:@"value"];
}


*: In fact, it does not really replace your instance, but instead use isa swizzling to transform your instance into a custom subclass that performs this work).





Le 30 mars 08 à 14:02, Chan-gu Lee a écrit :
Hi, all who concerns to my symptom.

Here is another issue related with this symptom.
I found additional stack frame called _NSSetIntValueAndNotify between callee of
setNumber: and setNumber:.
I think that it may cause Xcode step over the message of Objective-C class.
So, I decided to define another message whose name is setNewValue: at the same
place with setNumber:, and make call setNewValue: instead of setNumber:.


Here is replaced code.

- (IBAction)setNumber:(id)sender
{
	int new_number = [[m_TextField stringValue] intValue] ;
	[m_MyData setNewValue:new_number] ;
	// previouslt, it was [m_MyData setNumber:new_number] ;
}

When I tried with above code, it operated perfectly.
Is there a difference in the way of dispatching message between normal message and
property accessor?


Regards.
Chan-gu Lee

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: I can't step into any message of Objective-C object
      • From: Chan-gu Lee <email@hidden>
    • Re: I can't step into any message of Objective-C object
      • From: Chan-gu Lee <email@hidden>
References: 
 >Re: I can't step into any message of Objective-C object (From: Jeffrey Oleander <email@hidden>)
 >Re: I can't step into any message of Objective-C object (From: Chan-gu Lee <email@hidden>)

  • Prev by Date: Re: I can't step into any message of Objective-C object
  • Next by Date: Re: I can't step into any message of Objective-C object
  • Previous by thread: Re: I can't step into any message of Objective-C object
  • Next by thread: Re: I can't step into any message of Objective-C object
  • Index(es):
    • Date
    • Thread