extractZipFile problem

[d.healey]

I can confirm the issue on my system, can't extract to anywhere on the C drive. I'll keep investigating.

I've made a simple little test application for anyone who wants to play around with this. A test zip file is included in the project folder.

zipExtractor.zip

[d.healey]

@Lindon Yep you're correct. Add /MANIFESTUAC:level='requireAdministrator' to the linker flags section in Projucer and when your app starts you'll be prompted to give permission. Not sure how this will affect plugins, I'm going to test it now.

[Lindon]

@d-healey yeah I did this the other way(via VisualStudio)

and this seems to work too...

[d.healey]

@Lindon I tested in a plugin and it doesn't work. I assume that the plugin takes on the same privilege level as the host.

I'm going to test on MacOS now.

[Lindon]

@d-healey said in extractZipFile problem:

@Lindon I tested in a plugin and it doesn't work. I assume that the plugin takes on the same privilege level as the host.

I'm going to test on MacOS now.

-- test a stand alone on MacOS? yes? say yes, go on say yes...

[Lindon]

@d-healey said in extractZipFile problem:

@Lindon I tested in a plugin and it doesn't work. I assume that the plugin takes on the same privilege level as the host.

I think this may well be why NI Native Access and Arturia Software Centre etc. are stand alone programs only....they wont work as plugins because of this permissions issue...

[d.healey]

@Lindon

-- test a stand alone on MacOS? yes? say yes, go on say yes...

Yes. Just tested and it works fine, no permission issues. At least on my system.

I'm going to add that linker flag to my HISE fork's standalone template so it will automatically be added every time I export a standalone project.

[Lindon]

@d-healey - yeah I think MacOS is a bit more permissive than Windows - no surprise - it gets hacked a lot less.. but good to know, on to the next problem - well done.

[d.healey]

I've added a note about this to the docs - https://github.com/christophhart/hise_documentation/commit/0ced485944bc94c2bade19ab6a037d10c6db4c04

[Christoph Hart]

@d-healey yes but please don‘t make this the default - most people won‘t need admin access and it will look weird for a random eq plugin to ask for write access to the system folders.

[d.healey]

@Christoph-Hart I'm just making it the default on my fork, I'm not going to make a pull request. It's only in the standalone template, not the plugin template. At the moment everything I'm doing is with my standalone downloader so it's more convenient for me to have it as the default, I might change it in the future - or better yet use cmake ;)

[Christoph Hart]

@d-healey the proper solution would be to add a checkbox in the hise Project settings and then it will add those lines to the exporter template.

[d.healey]

@Christoph-Hart Ooo that's a good idea

[d.healey]

Looking at adding this now. Would an extra definition be better than a checkbox since it only applies to Windows?

[d.healey]

Ah I see why extra definitions aren't suitable. I'll just add a checkbox.

[d.healey]

Done - https://github.com/christophhart/HISE/pull/339

[Lindon]

@d-healey --sigh , now all sorts of permission problems on MacOS... so I dont think we are done here...

I cant get the app to write to any of the Plug-In folders....

So, all you MacOS experts ...how do I get my app to start with super user permissions....?

As far as I recall a WhiteBox generated installer (or MacOS when I try and start an installer) will ask for the password to start...

The error I am seeing is:

Failed to write to target file: /AAMyFirstProduct.vst3/Contents/Info.plist

[d.healey]

@Lindon I didn't have to do anything special on MacOS it just worked. Which OS are you testing on?

[Lindon]

@d-healey Mojave 10.14.5

-- researching now but I think you(we) will need to turn on sandboxing in the projucer file

[Lindon]

@Lindon - perhaps someone (anyone!) with MacOS experience can point me in the right direction ??