@Christoph-Hart said in Dynamically call Images instead ImageResources.dat:

Yes, use expansions for that. You don't want actual image files on an end user system.

How come? You mean for the ones that accidentally delete stuff? Or cause they have errors loading?

Wouldn't an image be able to be loaded just like a font is loaded? I got 3 different fonts for mac/Linux/Windows, works well.

@Rudra-Ghosh Ok.. (y)

@marcLab i forgot all about the source code folders :confounded_face:

@ulrik (y)

@Christoph-Hart If I set the LFO wave-selector to sin or anything else, it doesn't go back to the values given by the slider pack, even if I recompile.

Also if I set up something like a noise generator and and lfo modulating the gain, and I add a slider pack which I assign to the LFO modulator in the interface property, it doesn't work.

Do I have to add some code for this or is it supposed to work just by assigning the property in the interface editor?

Thanks,

u

@Christoph-Hart Thank you! You've been busy today!

@Tania-Ghosh any time.

@d-healey I would try out of curiosity but I will leave ch1. I do not use hr1 I did not manage to create the installer. for the extensions I will use the .hxi file and the sammle ch1 folder. and if I want to send extension updates I would just have to send a new hxi and a new sample

@d-healey nice, thanks :)

@orange Nope, it's just for sending a message to plugins saying "please change tune now". It's up to the plugin to change the tuning.

Right now HISE is good for dual monitors setup. When i work single Mac (13'') it becomes horrible to handle all DSP notes. I know custom workspace is needed but HISE slows down.
When I work windows 2 Monitors setup it works nice.

@ustk a 'sort-of' workaround is to use blank spaces in the tag name to enlarge the label's area.

@Christoph-Hart the tag's have a utilitarian feel to them, which isn't a problem per se, but perhaps being able to toggle their visibility would be a nice addition and have less impact on the Preset Browser's look on loading up.

Might also allow for two rows of tags as well....

@Christoph-Hart I'm going to have to try it now :p

@Christoph-Hart Oh I see, I'm trying...

@Christoph-Hart said in File system allow for binary write/load:

Encode the expansion, then run "Archive samples"

Is expansion encoding supposed to be implemented? I tried the button in the expansion toolbar but it always tells me I need to set an encryption key (which I have done).

I also had a look in the source and noticed that the expansion handler encode function looks like a placeholder, but there are other encoding functions in ScriptExpansion.cpp which look more complete.

@Lindon as an aside -- this (lazy) example above is also an example of how not allowing AppData to resolve to the project dir in development is massively inconvenient.

In development I can create as many presets as I like - and they are held in the project dir and I can load and save them. But the only way to delete them is to use the above code - which resolves to the compiled plug-ins App Data structure- where these presets are not yet saved.

Worse I can even (conceptually) get around the "dialog warning about overwriting presets" by deleting a preset (before saving it) and then saving anew with my new meta data, but of course it saves on one spot(project dir) and deletes in another(compiled plugin dir)...

So let me ask for another "Special Location" in:

FileSystem.getFolder(var locationType) can we please add project folder, which would resolve to - {PROJECT_FOLDER} as an option?