Re: inconsistencies in view renderings
Re: inconsistencies in view renderings
- Subject: Re: inconsistencies in view renderings
- From: Alan Snyder <email@hidden>
- Date: Wed, 19 Oct 2016 17:34:52 -0700
My goal is understanding, and I'm not quite there yet.
I tried changing my program to use a textured window, and the textured buttons now gray out when the window is inactive.
However, the buttons are not in the toolbar or a bottom margin. At least I don’t think they are in a bottom margin, unless the entire window excluding the toolbar is a bottom margin. The buttons are within a box with a fill color.
Do you have a test of a textured button in a textured window that does not gray out when inactive? (I’m ignoring the fact that textured buttons are not supposed to be used in the content area.)
I have also noticed that if I add a template icon to the textured button, then the text and the icon both gray out, even in a non-textured window.
However, if I use a textured segmented control with a label and a template icon, the label grays out but the icon does not.
Perhaps the intent is to gray out all textured buttons in inactive windows but the support is buggy?
Alan
> On Oct 18, 2016, at 8:53 PM, Quincey Morris <email@hidden> wrote:
>
> On Oct 18, 2016, at 19:43 , Alan Snyder <email@hidden <mailto:email@hidden>> wrote:
>>
>> Well, try this on Sierra:
>>
>> Use the Open File… menu item of Safari to open a dialog. Then activate a different application. On my system, the Cancel button in the dialog grays out (although it still looks different than the disabled Open button). Now click the Cancel button. Even though the button is grayed out, on my system the dialog is dismissed.
>
> Yup, that works as you say. Guess why? (You won’t like the answer.)
>
> The buttons change appearance when they’re in a window margin at the bottom of an inactive window (and, I would expect, when they’re in a toolbar at the top). If they’re in the body of the window, they don’t change.
>
> I’ve lost track of what the point is here. Apparently there is no programmatic way to control to inactive appearance, and “acceptsFirstResponder” only affects the inactive behavior. Is there something you were trying to do that you couldn’t, or was it only about explaining the apparent inconsistency?
>
_______________________________________________
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