I have a special situation where NSOpenPanel does not open a panel. The circumstances: My app is actually a screensaver, so it's run inside legacyScreenSaver. Also, it seems to occur only under macOS 10.15.0, and (perhaps) only for some users, not all.
What happens is that [oPanel runModal] does not open the panel, but I know from
the messages my screensaver saves in the log that it does get executed.
Instead, it seems to return directly/immediately with return code
NSModalResponseCancel.
Below is the relevant source code.
Question: does anyone have an idea what might be causing this strange behavior?
(It goes without saying that on my system everything runs fine, both on macOS
10.15.4 and macOS 11.3.1.)
Thanks a lot in advance.
Best regards, Gab.
Source code:
NSOpenPanel *oPanel = [NSOpenPanel openPanel];
[oPanel setAllowsMultipleSelection: NO];
[oPanel setCanChooseDirectories: YES];
[oPanel setCanChooseFiles: NO];
long int result = [oPanel runModal];
new_url = oPanel.URL;
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
