You could create an NSEvent and use the sendEvent method of NSApplication.

Override performFindPanelAction: in some class in the responder chain. In your override, if [sender tag] is NSTextFinderActionShowFindInterface, present your custom find panel. See the NSTextFinderAction enumeration for other possible actions.

You mean 13.6, there is no 14.6. Either Xcode 14.x or Xcode 15 will work on Ventura. Don't worry about .xip, if you double-click it, the Archive Utility will decompress it.

Yes, sandbox is required for the App Store. You need to read some documentation: https://developer.apple.com/documentation/security/app_sandbox/accessing_files_from_the_macos_app_sandbox

I forgot that I posted this question, and posted a similar question again: https://developer.apple.com/forums/thread/738561 This time I got a reply from an Apple engineer, saying that the defaults tool predates app groups, and they have a bug on file asking for an update.

Set the allowedContentTypes property, e.g., panel.allowedContentTypes = @[ UTTypeFolder ];

The warnings tell you that they are triggered by the compiler flag -Wdeprecated-builtins, so if you compile with the flag -Wno-deprecated-builtins, they should go away. Possibly Xcode 15 might have a checkbox for that flag; I’m not at a Mac right now. But if there’s no checkbox, you can use an “other c++ flags“ or something in the build settings.

The fact that CGDirectDisplayID is the same type as uint32_t does not mean that every uint32_t value is a legitimate display ID. If you want to find out something about displays, you should first get the display IDs of interest, with calls such as CGGetActiveDisplayList, CGGetOnlineDisplayList, or CGGetDisplaysWithPoint. By the way, since CGDisplayRotation is not behaving as documented, I filed a bug report, FB13202169.

When I tried your code in Xcode, it hung in the CGDisplayRotation(0) call. But when I changed that to CGDisplayRotation( CGMainDisplayID() ), it ran fine. What are you trying to accomplish by passing 0 as the display ID? Granted, the documentation says that it should return 0 if you pass an invalid display ID, but why tempt fate?

Does it happen on macOS?

I found an old sample project that draws a round window: https://www.cocoawithlove.com/2008/12/drawing-custom-window-on-mac-os-x.html It's old, so it needs a few obvious changes to make it compile with a recent Xcode. But it does work in a Sonoma beta. You may want to see how this compares with your code.

You may want to set the ignoresMouseEvents property of the window.

You can write to the console log using NSLog or os_log. What programming language are you using?

For the first thing, finding the running app’s own location, you can use NSBundle.mainBundle.bundleURL. Typed from memory, away from my Mac.

Instead of NSNotificationCenter.defaultCenter, use NSWorkspace.sharedWorkspace.notificationCenter.