All developers participating in the HISE Betatest Program
@Christoph-Hart said in Asset Manager:
A big XML file would be a bit tricky though - you can never change that template file because it would never be updated
Good point. Maybe I'll just use another script and the Builder stuff to construct the template's module tree instead.
@David-Healey that should be covered by that wildcard function, any file that matches against that wildcard would be excluded from the deinstallation procedure (and before installing it checks if it exists, then does nothing). A big XML file would be a bit tricky though - you can never change that template file because it would never be updated - with script files you can branch out your config stuff into a seperate smaller file.
@Christoph-Hart In addition to script files I can see a situation where I would want to include a project xml as a starting template. So that would be another file I'd want to allow the user to change.
@Jeetender eaiest way is ro use a scriptnode network and a xfade module...
@boim98208 The export wizard has been removed from the latest version of HISE a few days ago. Remove the version you have and start over with a fresh build.
Right but the math works the same way.
All you need to do is find the right hise functions in the API for the math calls.
@David-Healey should this also extend to preprocessor definitions? I think currently it removes them but there might be a case for a similar usage there
@David-Healey yes good idea. So ideally you could define a wildcard for user editable config files - if they dont exist they are copied over but they are not deleted / overriden when updated or uninstalled.
