• 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: Creating NSButton in Code does not set controlTint to currentControlTint
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Creating NSButton in Code does not set controlTint to currentControlTint


  • Subject: Re: Creating NSButton in Code does not set controlTint to currentControlTint
  • From: Quincey Morris <email@hidden>
  • Date: Thu, 26 Dec 2013 20:06:26 -0800

On Dec 26, 2013, at 18:49 , Peter Teeson <email@hidden> wrote:

>> On Dec 26, 2013, at 09:49 , Peter Teeson <email@hidden> wrote:
>>> Sets the receiver’s control tint.
>>> - (void)setControlTint:(NSControlTint)controlTint
>>> Parameters
>>> controlTint
>>> An Designated Initializers value that specifies the tint of the receiver.

> What should I say if I'm going to file a bug report?

I believe it’s simply meant to say “A NSControlTint value that specifies the tint of the receiver.”

> Why does it show the Aqua tint if I set up the exact same button using IB and let it be instantiated from the nib?

I think Uli has your answer, that it’s doing what it’s supposed to do under the given circumstances, out of a larger universe of possible appearances. My *guess* is that the IB-created button is in a XIB with a format designation of an earlier Xcode/target OS, so it’s following different rules than the rules used for programmatic creation.

Or, it could simply be that you’re using the wrong combination of button attributes — the maze of interactions between those properties is fairly headache-full. Try Keary’s suggestion of creating the button in IB, and use the debugger to examine the properties of the IB-created button that does look like what you intend.

However, also consider Uii’s other, implied point: you may be wasting your time because the concept of button tinting in current versions of OS X has simply gone away. Avoiding a deprecated graphite appearance by implementing a deprecated aqua appearance seems like the wrong direction to head.


_______________________________________________

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


  • Follow-Ups:
    • Re: Creating NSButton in Code does not set controlTint to currentControlTint
      • From: Kyle Sluder <email@hidden>
References: 
 >Creating NSButton in Code does not set controlTint to currentControlTint (From: Peter Teeson <email@hidden>)
 >Re: Creating NSButton in Code does not set controlTint to currentControlTint (From: Keary Suska <email@hidden>)
 >Re: Creating NSButton in Code does not set controlTint to currentControlTint (From: Peter Teeson <email@hidden>)
 >Re: Creating NSButton in Code does not set controlTint to currentControlTint (From: Quincey Morris <email@hidden>)
 >Re: Creating NSButton in Code does not set controlTint to currentControlTint (From: Peter Teeson <email@hidden>)

  • Prev by Date: Re: Creating NSButton in Code does not set controlTint to currentControlTint
  • Next by Date: Re: Creating NSButton in Code does not set controlTint to currentControlTint
  • Previous by thread: Re: Creating NSButton in Code does not set controlTint to currentControlTint
  • Next by thread: Re: Creating NSButton in Code does not set controlTint to currentControlTint
  • Index(es):
    • Date
    • Thread