Hise general and compiler settings not saving

[whoopsydoodle]

This post is deleted!

[David Healey]

@whoopsydoodle

Close HISE.
Rename the HISE app data folder to HISE-old.
Open HISE and change the settings.
Close/Reopen HISE and check if it worked.

[whoopsydoodle]

@d-healey You mean the settings folder that on Mac is in application support, right? I already thought about that and tried it.

I renamed the old folder and HISE didn't create a new one. Settings still not saved.

[David Healey]

@whoopsydoodle said in Hise general and compiler settings not saving:

HISE didn't create a new one.

That's weird. You sure it's the right folder? You can find the one HISE is using from the link in the File menu.

[whoopsydoodle]

@d-healey Following that option in the file menu brings me to a new different location. It now makes a folder when I hit that. But the folder is empty. It's not saving any config files inside it.

[David Healey]

@whoopsydoodle I think there's something wrong with your HISE setup. I suggest removing all copies of HISE, the source code, and the config files (backup the config if you have any customisations). Then restart with a fresh clone of the develop branch.

[whoopsydoodle]

@d-healey Yah I'm assuming that must be the case. I'm going to try a fresh pull and build.

[Kaih]

OSX Tahoe 26.5.2 M2 HISE 3deb6f2a

Had the same issues just today after few updates from much older version.
The cog wheel settings not saving at all and snippet + document bowsers not working.
Did few rebuilds, but the solution is to create a new empty HISE folder to
'/Users/yourUserName/Library/Application Support/HISE' and start HISE again.
After putting in the settings again, it will populate the folder with the necessary files.

Why the folder has vanished is anyones guess, the easiest solution is to blame disc cleaning and maintenance softwares if you use one and you probably wouldn't be far off.

[Christoph Hart]

@Kaih looks like a permission issue, if the app data folder was created from another user (or from a user with admin privileges), you cannot write to it. thanks for nothing macOS...

[Kaih]

@Christoph-Hart
Yes, you're quite right, that probably is the real cause.
Still a bit weird, since an older install worked as should.
Although it was the one with an .pkg, or was it .dmg, installer from the website,
so that might have to do with it as well.
And as the admin and the sole user of the machine, the writing rights should've been ok.