@orange said in Qt Installer framework:

Personally, I do not see any additional advantage

You only have to learn a single installer platform instead of learning a separate one for each OS. It will also look more similar on each system so a user moving from Windows to Mac for example will get a similar experience on both.

@trillbilly export a simple plugin and have them try it. See if it's hise or if it's whatever you did in your actual project

@parabuh said in Windows Code Signing Certificate:

@oskarsh even if you want cert like this you need be company and get a lot government papers, so if you are sole proprietor you can't sign your code.

-- er not true.

@d-healey Some fonts are multiligual and since they are also including non-Latin char sets they use wider metrics. This may end up with different scaling on the different Operating systems. I see that issue especially on the Devanagari type fonts which means they may need to have larger vertical metrics than ordinary Latin fonts, due to stacking conjuncts and mark positioning. This issue also happens on the different web browsers too.

aac4c7b8-6f6d-11e6-9e49-a1ce330b39e8.png

Maybe getting the Latin-only versions of the fonts (if you use only Latin chars in your plugin) could help but I am not sure if it works for every font.

If it is a Google font, you can get Latin-only versions from the Google Webfont Helper here: https://google-webfonts-helper.herokuapp.com/fonts/poppins?subsets=latin

To keep my Software Code safe, I have been using an Individual Code Signing certificate for the last two years from signmycode.com.

I think instead of using AUDIO_FILES you should use the {PROJECT_FOLDER} wildcard like with sample maps. That may resolve the / \ issue too. I don't have a suitable project setup to test this so let me know if it solves it.

Go to the export menu and select Export as Instrument. I'm assuming you've already compiled HISE from source before and therefore have everything setup to export.