Re: All buttons lost focus ring on Yosemite

> On Feb 12, 2015, at 6:40 AM, Dragan Milić wrote: > > I’m dealing with a rather strange issue. When running my application on > Yosemite, all buttons lose focus ring (when having focus). When I say all, I > mean absolutely ALL buttons, even those in standard alert panels and sheets. > I can

Re: NSWindowControllers and NSWindow

> On 17 Feb 2015, at 1:17 am, Dave wrote: > > My initial thought were to have a WindowController: > > LTWMainWindowController that looks after a number of Windows. Initial there > is just one window LTWWindowX (but I want to add others in the future, > LTWWindowY, LTWWindowZ, etc.), each wind

Re: NSWindowControllers and NSWindow

> On 17 Feb 2015, at 5:59 am, Quincey Morris > wrote: > >> On Feb 16, 2015, at 12:30 , Ken Thomases wrote: >> >> A view controller and its view should be reusable in different contexts, or >> at least designed as though it might be. > > To round out the larger discussion for posterity, I

Re: NSWindowControllers and NSWindow

On Feb 16, 2015, at 12:30 , Ken Thomases wrote: > > A view controller and its view should be reusable in different contexts, or > at least designed as though it might be. To round out the larger discussion for posterity, I’d add that when using an OS X storyboard, the picture is a little bit d

Re: NSWindowControllers and NSWindow

> On Feb 16, 2015, at 2:38 PM, Jens Alfke wrote: > > I’m surprised by how complicated the discussion is making this seem! Me too ! -rags ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments

Re: BOOL attribute types.

> On Feb 16, 2015, at 1:27 PM, Akis Kesoglou wrote: > > objc.h typedefs BOOL as char/bool, as David says, so I don’t think you can > infer that a property is BOOL by introspecting the property — you’ll always > see char or bool. I’ll chime in too — there’s no way to tell the difference. If yo

Re: NSWindowControllers and NSWindow

> On Feb 16, 2015, at 9:55 AM, Dave wrote: > > I can see I could do it if I had LTWViewController.xib that included an > NSWindow? I’m surprised by how complicated the discussion is making this seem! All you need to do is create an NSWindowController subclass in Xcode, check the “Also crea

Re: BOOL attribute types.

class-dump [1] properly dumps properties as BOOLs where appropriate. Just had a quick look over the code but didn’t find anything particular to help you out, but you might want to take a look yourself. [1] https://github.com/nygard/class-dump > On 16 Φεβ 2015, at 23:27, Akis Kesoglou wrote:

Re: BOOL attribute types.

> Yeah. Thanks. > > What I'm asking is how can I identify the property as a BOOL when analyzing > property structures so that I can output "BOOL" to a descriptive string and > if I analyze a char, I can output "char" as a descriptive string. > > Obviously, I can't use property_getAttributes()

Re: BOOL attribute types.

> On Feb 16, 2015, at 1:06 PM, Alex Zavatone wrote: > > Xcode 5.1.1 > IOS 7.x > > I'm messing with an auto description category for NSObjects with the interest > of dumping out a class's properties in the format of property name, property > class and string equivalent of property value. > >

Re: BOOL attribute types.

Yeah. Thanks. What I'm asking is how can I identify the property as a BOOL when analyzing property structures so that I can output "BOOL" to a descriptive string and if I analyze a char, I can output "char" as a descriptive string. Obviously, I can't use property_getAttributes() since it retur

Re: BOOL attribute types.

> On Feb 16, 2015, at 1:06 PM, Alex Zavatone wrote: > > Xcode 5.1.1 > IOS 7.x > > I'm messing with an auto description category for NSObjects with the interest > of dumping out a class's properties in the format of property name, property > class and string equivalent of property value. > >

BOOL attribute types.

Xcode 5.1.1 IOS 7.x I'm messing with an auto description category for NSObjects with the interest of dumping out a class's properties in the format of property name, property class and string equivalent of property value. I'm also considering supporting scalar primitive types that are not NSObj

Re: NSWindowControllers and NSWindow

Excellent suggestions, as usual. Thanks, Ken! > On Feb 16, 2015, at 3:30 PM, Ken Thomases wrote: > > He clearly says that the MainMenu NIB should _not_ include a window: I thought I remembered that, but when I went back for a quick check I missed the passage you quoted. That must be where I g

Re: NSWindowControllers and NSWindow

On Feb 16, 2015, at 12:39 PM, Bill Cheeseman wrote: > Although I follow Mike Ash's advice, I have separate MainMenu.xib and > MainWindow.xib files instead of a single window.xib file. My MainMenu.xib > contains the application's menu bar but no window. The construction of this sentence suggest

Re: NSWindowControllers and NSWindow

> On 16 Feb 2015, at 18:39, Bill Cheeseman wrote: > > Although I follow Mike Ash's advice, I have separate MainMenu.xib and > MainWindow.xib files instead of a single window.xib file. My MainMenu.xib > contains the application's menu bar but no window. MainMenu.xib is owned by > NSApplicatio

Re: NSWindowControllers and NSWindow

> Well, you've switched from talking about a window controller to a view > controller for some reason. Sorry, was a typo I meant LTWWindowController, I’m so used to typing ViewController that I guess my fingering did the thinking in this case! Fixed the warnings too, thanks again for your hel

Re: Idea for Improving Vibrancy

On Feb 16, 2015, at 5:34 AM, Roland King wrote: > And for anyone, like me, who doesn't like the vibrancy effect, you can turn > it off in preferences. Is this the right setting: “◽ Disable Windows® look and feel” -Carl ___ Cocoa-dev mailing list (

Re: NSWindowControllers and NSWindow

On Feb 16, 2015, at 11:55 AM, Dave wrote: >> You never want a NIB for the window controller that's separate from the NIB >> containing the window. You want a single NIB for the window which the >> window controller will load and be the owner of. The NIB will *not* >> "contain" the window con

Re: NSWindowControllers and NSWindow

On Feb 16, 2015, at 13:20:24, Dave wrote: > > Thanks, I solved it, the File’s Owner didn’t take for some reason, I did it > again and it seems to work ok now. > > However, I’m guessing that something isn’t right, since I now get two > warnings - > > /path/LTWMainWindow.xib: The initial posi

Re: Idea for Improving Vibrancy

Ugh. Mail used the wrong address again and bounced this... -- Seth Willits > On Feb 15, 2015, at 9:54 PM, Seth Willits wrote: > > On Feb 15, 2015, at 6:13 AM, Charles Jenkins wrote: > >> Is this possible, do you think, to open a window that always hides directly >> behind the working wind

Re: NSWindowControllers and NSWindow

Thanks, I solved it, the File’s Owner didn’t take for some reason, I did it again and it seems to work ok now. However, I’m guessing that something isn’t right, since I now get two warnings - /path/LTWMainWindow.xib: The initial position of this window is outside of this machine's screen. a

Re: NSWindowControllers and NSWindow

> On Feb 16, 2015, at 10:24 AM, Dave wrote: > > Thanks for this, it seems to be saying there is no need for a separate Window > Subclass and that the Window Controller Subclass contains all the code needed > to drive the window. I’m a bit confused of when to use an NSWindow and when > to use

Re: NSWindowControllers and NSWindow

> On Feb 16, 2015, at 12:55 PM, Dave wrote: > > LTWViewController.h and LTWViewController.m, and LTWWindow.xib, then set the > file owner in the NIB to “LTWViewController”, how do I then wire up outlets, > bindings and actions so that I get properties set in LTWViewController? Connect the UI

Re: NSWindowControllers and NSWindow

> You never want a NIB for the window controller that's separate from the NIB > containing the window. You want a single NIB for the window which the window > controller will load and be the owner of. The NIB will *not* "contain" the > window controller. The File's Owner placeholder in the NI

Re: NSWindowControllers and NSWindow

> On Feb 16, 2015, at 6:17 AM, Dave wrote: > > My initial thought were to have a WindowController: > LTWMainWindowController that looks after a number of Windows. Usually you have a separate NSWindowController subclass for each distinct type of window. If the windows share some functionality,

Re: NSWindowControllers and NSWindow

On Feb 16, 2015, at 09:24:36, Dave wrote: > > Thanks for this, it seems to be saying there is no need for a separate Window > Subclass and that the Window Controller Subclass contains all the code needed > to drive the window. I’m a bit confused of when to use an NSWindow and when > to use and

Re: NSWindowControllers and NSWindow

On Feb 16, 2015, at 9:24 AM, Dave wrote: >> I recommend that you follow the advice in this article: >> . > > Thanks for this, it seems to be saying there is no need for a separate Window > Subclass and tha

Re: NSWindowControllers and NSWindow

Hi Ken, Thanks for this, it seems to be saying there is no need for a separate Window Subclass and that the Window Controller Subclass contains all the code needed to drive the window. I’m a bit confused of when to use an NSWindow and when to use and NSWindowController? The way I had thought

Re: NSWindowControllers and NSWindow

On Feb 16, 2015, at 8:17 AM, Dave wrote: > I’ve just started a new Application and I”m wondering what the best/standard > way of setting it up. I recommend that you follow the advice in this article: . Ch

NSWindowControllers and NSWindow

Hi All, It’ s been a while since I worked on the Mac as I’ve been mostly in the iOS world lately. I’ve just started a new Application and I”m wondering what the best/standard way of setting it up. My initial thought were to have a WindowController: LTWMainWindowController that looks after a

Re: Idea for Improving Vibrancy

Hmm this thread is rapidly heading towards moderation - like the last one we had on vibrancy. To the original poster - nice that you made the suggestion/bug report to Apple, I don't think you're going to get far with that but who knows. I think the effort involved in rolling your own moving wi

Re: Idea for Improving Vibrancy

I'm so happy I'm not the first guy to think "kill it". Kill it. On Feb 16, 2015, at 7:17 AM, Greg Weston wrote: >>> I have an idea for improving vibrancy >> >> Me too. Kill it. > > Ditto. I look at vibrancy as Apple showing Microsoft how to do Glass right > without questioning whether it shou

Re: Idea for Improving Vibrancy

>> I have an idea for improving vibrancy > > Me too. Kill it. Ditto. I look at vibrancy as Apple showing Microsoft how to do Glass right without questioning whether it should be done at all. To me, "consume extra resources in order to reduce the usability of the system" is a fundamentally flaw