Wrapping NSOpenPanel
/NSSavePanel
in a bundle that can access the
more powerful macOS APIs has its uses though.
Oi vey! don’t do that.
While this is a commonly used technique, it puts you on very shaky ground compatibility-wise. In practice, the risk level varies based on how far up the software stack you are. Using this technique for low-level stuff is technically not supported but less likely to cause problems in practice. OTOH, using it for high-level stuff is very likely to cause compatibility problems in practice, if not today then in some future iteration of macOS. The open and save panels are right at the top of the software stack, where you are most likely to encounter issues.
If UIKit’s open and save panel APIs don’t meet your requirements, I recommend that you file an enhancement request for the features you need. Please post your bug number, just for the record.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"