appkit

I'm implementing a custom NSMenuItem view that shows a highlight as the user mouses over it. To do this, the code calls NSRectFill after setting [NSColor selectedMenuItemColor] as the active color. However, I noticed that the result is not simply a solid color — it actually draws a gradient instead. Very nice, but wondering how this "magic" works — i.e. if I wanted to define my own color that didn't just draw solid, how would I? I don't know how this actually works, but I found a way to replicate the behavior with custom gradients (or any other drawing operations). The "trick" is to use a

Is the resize mouse cursor used by Preview (e.g. when resizing shapes) a system cursor? It's not available directly as a method in NSCursor but then it doesn't look like there's a private resource for the cursor in the Preview app's bundle either.. Are there more system cursors other than the methods defined by the NSCursor class..? I think you are particularly interested in these class methods (Preview.app dissasembly). +[NSCursor resizeAngle45Cursor]; which calls +[NSCursor _windowResizeNorthEastSouthWestCursor]; +[NSCursor resizeAngle135Cursor]; which calls +[NSCursor

In Cocoa/AppKit, given a screen from [NSScreen screens] , how can I find out if there's a full-screen app running on that specific screen? I'm mostly interested in apps that use the Cocoa APIs for full-screen, but if there's a solution that also encompasses other types of full-screen apps, even better. The solution needs be able to pass Mac App Store approval. My specific use case involves a menu bar app ( NSStatusItem ) and figuring out whether or not a menubar is shown at all on [NSScreen mainScreen] in order to allow a global keyboard shortcut to show either a popover positioning on the

I added a applicationShouldOpenUntitledFile method to my application delegate, returning NO as Apple's documentation specifies. However, I'm still getting a new document on startup. What's wrong? @implementation AppDelegate @synthesize window; - (void)applicationDidFinishLaunching:(NSNotification *)aNotification { NSLog( @"This is being called" ); } - (BOOL)applicationShouldOpenUntitledFile:(NSApplication *)sender { NSLog( @"This never is" ); return NO; } @end You're running Lion. When you ran before adding the applicationShouldOpenUntitledFile handler, a new document was created. Now, with 10

Right - so I've created a help book, did all the right things , double-checked my plist and index.html files, and all I get is the notorious The selected topic is currently unavailable. The only entry in Console when attempting to open the help book is a plain 3/8/15 1:23:42.467 PM HelpViewer[35015]: Couldn't find book with this ID: (null) Not too helpful. Where to go from here? Are there any debugging techniques for Apple Help? Logging to turn on? Anything..? Just struggled a few hours with the same problem. The ID: (null) means that you are missing CFBundleName or HPDBookTitle keys, or