Not sure how you've setup your controls, but this should also fire the callback of the button which triggers the page swap.

Nah, VirtualBox will 100% not work correctly. Even if it loads, there are some many things (like the native UI rending or core audio drivers) that will make it a terrible experience.

The best bang for the buck Apple hardware are used mac minis (the older ones from 2012. Pick up an i7 with 16GB RAM and you're set for development).

I am working with Sierra, and it runs smoothly here. Sometimes new OS updates break minor things (Sierra for example didn't render the code font with font size 15.0 which made the scripting code invisible), but apart from these glitches different macOS versions are not a regular source of trouble

It depends on your requirements for performance. If you use the SimpleGain module the sounds are still rendered. Bypassing it kills all voices but toggling it during playback might be a little bit clunky.

Another option is using the MIDI Muter module which mutes incoming notes but doesn‘t kill any voices, at the end it comes down to how you want your instrument to behave...

@d-healey said in Floating Tile Button:

If you set the saveInPreset property to true for the button you want to be enabled on init and all the others to false.

Hate to be picky, but that's not good advice. All controls related to UI handling (page swapping, making other elements visible, etc) must not have saveInPreset enabled, or the interface will do random things if you load user presets.

Instead, leave saveInPreset to false, and call setValue() for the given control directly in the onInit callback:

const var page1Button = Content.getComponent("page1Button");
const var page2Button = Content.getComponent("page2Button");
const var page3Button = Content.getComponent("page3Button");

page1Button.setValue(1); // or whatever logic you need
page1Button.changed();

Ah I forgot to enable mouse callbacks. Just add this line somewhere:

PresetDisplay.set("allowCallbacks", "Context Menu");

Fresh from the source:

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

PresetDisplay.setPaintRoutine(function(g)
{

	g.fillAll(0xFF111111);	
	
	g.setColour(Colours.white);
	
	g.drawAlignedText(this.data.text, [0, 0, this.getWidth(), this.getHeight()], "centred");
	
});

PresetDisplay.startTimer(200);

PresetDisplay.setTimerCallback(function()
{
    var text = Engine.getCurrentUserPresetName();
	
    if(text == "")
	text = "Init";
	
    if(this.data.text != text)
    {
        this.data.text = text;
        this.repaint();
    }
});

const var presetBrowserData = 
{
  "Type": "PresetBrowser",
  "Title": " ",
  "FontSize": 16,
  "ColourData":
  {
    "bgColour": "0xDD111111",
    "itemColour1": "0xFF46C0D8",
    "itemColour3": "0x3346C0D8"
  }
};

PresetDisplay.setPopupData(presetBrowserData, [PresetDisplay.getWidth()/2, 25, 800, 470]);

Nope, no demo functionality with the serial key system for the reason Tod mentioned plus the increased chance of piracy for software that can be unlocked by removing the demo check.

That one?

https://forum.hise.audio/topic/499/multiple-page/9

Use a DAW and an audio track.

Ah yes running a XMl validator is the thing I would have suggested too