I have a project that needs updating on Mac side to accommodate Mx chips natively, thus far it's been the Intel code Rosetta'd.
This is non-JUCE/iPlug code, from a dated but stable codebase. Have a VST and a standalone simple host that loads the plugin. Has been working as desired.
I now have a macmini with M1, running Ventura/OSX13, XCode 15. Loaded up all the old projects, made the necessary adjustments, recompiled. Once all the obligatory link tomfoolery is passed I have an Intel/Apple .vst and .app. All is well with the world.
There are dialogs for serial number (created on the fly) and locating a sound library (using openPanel). They don't appear to fire.
If I load the VST using a third party host/DAW the dialogs show, whether running Apple or Rosetta. Using our own standalone code - they don't.. They just return that the dialog was cancelled.
There's nothing odd about the invoking code..
Code: Select all
NSOpenPanel* op = [NSOpenPanel openPanel];
[op setAllowsMultipleSelection:NO];
[op setCanChooseFiles:NO];
[op setCanChooseDirectories:YES];
[op setShowsHiddenFiles:YES];
[op setShowsResizeIndicator:YES];
[op setShowsToolbarButton:YES];
const gfl::String& fp = inPath.GetString();
NSURL* furl = [NSURL fileURLWithPath:(NSString*)fp.GetCFString()];
[op setDirectoryURL:furl];
if([op runModal] == NSModalResponseOK /*NSFileHandlingPanelOKButton*/)
{
NSURL* url = [op URL];
mFilePath = gfl::FilePath([[url path] UTF8String]);
return USER_SELECTED;
}
return USER_CANCELLED;
I'm assuming it must be something changed about how one sets up an application or main form, some attribute or capability, or perhaps how the UI thread is invoked.
I see a few others having runModal issues recently on Apple & StackEx posts, but their solutions seem opaque or just unresolved.
Anyone else had this? Any ideas?
DSP
