• 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: [nextCue setFloatValue:0.0]; doesn't work
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [nextCue setFloatValue:0.0]; doesn't work


  • Subject: Re: [nextCue setFloatValue:0.0]; doesn't work
  • From: "Michael Ash" <email@hidden>
  • Date: Wed, 24 May 2006 12:24:24 -0400

On 5/24/06, Michael Swan <email@hidden> wrote:
I have a project that refuses to work in.

I deleted the NSTextField, made a new one and reconnected it.
I used copy and paste to make sure that I had not misspelled the
outlet name.
I cleaned all targets
I have other NSTextFleid objects that work just fine.

Did you actually make sure that the outlet is non-nil, by logging it or checking it in the debugger?

Reaching further out on a limb, it sounds like you may have a method
named setNextCue: which does not set your outlet. This confuses the
key-value coding machinery and results in new outlets. See
http://www.cocoadev.com/index.pl?IBOutletNSViewIsNil for more details
on what I'm talking about.

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

This email sent to email@hidden

References: 
 >[nextCue setFloatValue:0.0]; doesn't work (From: Michael Swan <email@hidden>)

  • Prev by Date: Re: Xcode 2.3 and May Documentation Update
  • Next by Date: Re: Xcode 2.3 and May Documentation Update
  • Previous by thread: [nextCue setFloatValue:0.0]; doesn't work
  • Next by thread: editing plist file
  • Index(es):
    • Date
    • Thread