Bundle Identifier wont set on MacOS
-
The problems with develop go on....
Now the Preferences panel refuses to accept a new bundle identifier
-
@lindon Another one that's never been fixed... You have to edit the XML directly
-
@ustk which XML?
-
@lindon
project_info.xml
-
@ustk yeah thanks found it already..
-
@lindon just enter your bundle identifier and press 'cancel' when HISE tells you it's wrong. It will keep your ID in the preferences.
Never had any problem doing so... -
@matt_sf thanks, but this is now the least of my problems.....
https://forum.hise.audio/topic/5390/plugin-wont-set-up-samples-in-macos/7
-
@lindon Is this issue only on Windows or is it on Mac?
The cause is almost certainly down to a regex difference between different OSs.
This is the check in the source code. I'm rubbish at regex but I don't think it would be difficult to figure out a fix to this.
if (id == Project::AppGroupID || id == Project::BundleIdentifier) { const String wildcard = (id == HiseSettings::Project::BundleIdentifier) ? R"(com\.[\w\d-_]+\.[\w\d-_]+$)" : R"(group\.[\w\d-_]+\.[\w\d-_]+$)"; if (!RegexFunctions::matchesWildcard(wildcard, newValue.toString())) { return Result::fail(id.toString() + " doesn't match the required format."); }
-
I wonder if this
com\.[\w\d_]+\.[\w\d_]+$
orcom\.[\w\d-\w\d]+\.[\w\d-\w\d]+$
would work... I'm not even sure the\d
is needed because I think\w
covers all alphanumeric characters. -
@d-healey - oh its so tempting to say;
"oh yeah that might work.."and sound like I know anything useful about regex...but I'll stick to the more honest..
"I have absolutely no idea......"
:-)
-
@lindon I'll test it later and if it works I'll make a pull request.
-
Problem only appears on MacOS. I changed the regex and the problem goes away. https://github.com/christophhart/HISE/pull/247