loadUserPreset - strange behaviour...

[Dan Korneff]

Hey guys. I'm just starting to add user presets to my project. Having a little trouble getting them to load with a combo box.
I've created 2 user presets in the PresetBrowser, but the interface designer doesn't show any control changes.
Here's what I'm doing:

const var ComboBox1 = Content.getComponent("ComboBox1");

const var list = Engine.getUserPresetList();

inline function onComboBox1Control(component, value)
{
    switch (number)
	{
		case 1:
		Engine.loadUserPreset(list[0]);
		break;

		case 2:
		Engine.loadUserPreset(list[1]);
		break;
	}
};

Content.getComponent("ComboBox1").setControlCallback(onComboBox1Control);

[Lindon]

@dustbro have you checked that list elements contain the correct data? Bit obvious but still...

[d.healey]

@dustbro

    switch (number)
	{
		case 1:
		Engine.loadUserPreset(list[0]);
		break;

		case 2:
		Engine.loadUserPreset(list[1]);
		break;
	}

Use this instead : Engine.loadUserPreset(list[number-1]); it's not a fix to the issue it's just a much shorter way of writing the same thing. Where are you getting number from though?

[Dan Korneff]

@Lindon I believe so:

[Christoph Hart]

Protip: Rightclick on the row in the table to get a popup with the data for arrays and objects :)

[Dan Korneff]

@d-healey said in loadUserPreset - strange behaviour...:

Where are you getting number from though?

I thought the number was the position of the selected combo box?

[Christoph Hart]

@dustbro said in loadUserPreset - strange behaviour...:

I thought the number was the position of the selected combo box?

The combobox has a index starting with 1 because 0 marks "no selection".

[d.healey]

@dustbro

I thought the number was the position of the selected combo box?

In this function the first time the word number appears is inside the switch. I think you want to replace number with value.

inline function onComboBox1Control(component, value)
{
    switch (number)
	{
		case 1:
		Engine.loadUserPreset(list[0]);
		break;

		case 2:
		Engine.loadUserPreset(list[1]);
		break;
	}
};

[Dan Korneff]

@d-healey said in loadUserPreset - strange behaviour...:

I think you want to replace number with value.

If I replace number with value, HISE crashes when I compile the script

[Dan Korneff]

Even if I ditch the array
this = instant HISE crash:

inline function onComboBox1Control(component, value)
{
    switch(value)
	{
		case 1:
		Engine.loadUserPreset("asdf/Bass/BassLeveler");
		break;

		case 2:
		Engine.loadUserPreset("asdf/Drums/DrumPump");
		break;
	}
};

Content.getComponent("ComboBox1").setControlCallback(onComboBox1Control);

[Lindon]

@dustbro yeah HISE crashes like a 0.1 app when I use loadUserPreset

[Dan Korneff]

@Lindon :( Using the Preset browser floating tile works as expected... but my GUI only has room for a simple combo box.
not sure what I'm doing wrong

[d.healey]

@dustbro yeah must be some bug with the load preset function. But value is definitely right since number doesn't exist

[Lindon]

@dustbro As Dave pointed out to me, using:

storeAllControlsAsPreset("abc",false);

and
restoreAllControlsAsPreset("abc");

seems to be more reliable - try substituting those?

[Dan Korneff]

@Lindon I'll give that a try.
Is it required to use storeAllControlsAsPreset if the preset files already exist?

[Dan Korneff]

@Christoph-Hart Is there an example of the CustomUserPreset tutorial that uses a combobox instead of the Viewport?

[Lindon]

@dustbro dont think so you could just give the Restore option a try...

[d.healey]

I'm having a go at making a custom preset browser, the first issue I've hit is storeAllControlsAsPreset() doesn't allow a folder structure with the file name, so all presets end up in the top level. Is there a known workaround for this?