Look and Feel - Toggle Buttons and the MIDI Sources panel...

[Lindon]

It would seem that the MIDI Sources panel uses a default toggle button to represent the selected device - in a way that the MIDI Channel List doesnt....

So when I laf my toggle buttons to do what I want - it breaks the MIDI Sources panel...

see the "button" next to KeyLab 49....

Adendum - laf also seems to break the Custom Settings too - meaning they wont show up correctly...

[ustk]

@Lindon Yeah same issue... The tick boxes of the MidiSources tile react to the LAF which isn't desirable...

[ustk]

@Lindon That's fixed, I made a pull request...

[Lindon]

@ustk great. Well done. Can you let us know when its included.

[Lindon]

Any news on this fix?

[ustk]

@Lindon It's not yet merged, but if you can't wait, just remove or comment out this line:

[Lindon]

@ustk ok thanks - given the Custom Settings is alos broken I assume I need to comment out line 53 too?

CustomSettingsWindowPanel::CustomSettingsWindowPanel(FloatingTile* parent) :
	FloatingTileContent(parent)
{
	setDefaultPanelColour(PanelColourId::bgColour, Colours::black);
	setDefaultPanelColour(PanelColourId::textColour, Colours::white);

	addAndMakeVisible(viewport = new Viewport());

	window = new CustomSettingsWindow(getMainController(), parent->shouldCreateChildComponents());

	viewport->setViewedComponent(window);
	viewport->setScrollBarsShown(true, false, true, false);

	if (getMainController()->getCurrentScriptLookAndFeel() != nullptr)
	{
		slaf = new ScriptingObjects::ScriptedLookAndFeel::Laf(getMainController());
		viewport->setLookAndFeel(slaf);    <<<<<<--- this one....
	}

	window->setFont(GLOBAL_BOLD_FONT());

	
}

[ustk]

@Lindon Haven't tested, do it and tell me ;)

[Lindon]

damn it - it turns out its way worse than I thought...

So its all over the buttons in all the modulators too...

[ustk]

@Lindon probably more lines 50 to 54...

[Lindon]

@ustk so in your edit that would mean lines 279-284

Now to find where the modulators are using the laf....

[Lindon]

Well nothing obvious is jumping out at me...@Christoph-Hart ??

[Lindon]

Any chance of getting this looked at? - otherwise the look and feel is actually broken - in that it might work on your project but it screws the HISE interface completely - making it very very hard to work with.

[d.healey]

@Lindon This is why I never use it. It should have no effect on the IDE interface in my opinion.

[ustk]

It's not only this, the popups too and their buttons, and a lot of things...
It's because the buttons/sliders used are the same in front/backend and the laf aren't separated. it should be doable but it might require a lot of redundant modifications...

[Christoph Hart]

You can reset the look and feel so that it looks right until the next time you compile, which should solve most workflow issues.

The problem is that the look and feel is global so it would be a massive rewrite in order to fix it.

[Lindon]

@Christoph-Hart - then its not really worth having is it - I might as well just use customer painted panels..

[Christoph Hart]

Why? If you want to change anything in the module tree, reset the look and feel, until you work on the UI again, then recompile the script.

[Lindon]

@Christoph-Hart said in Look and Feel - Toggle Buttons and the MIDI Sources panel...:

Why? If you want to change anything in the module tree, reset the look and feel, until you work on the UI again, then recompile the script.

yes - sure but nothing I do (including commenting out the LaF where @ustk and I identified) does not solve this problem:

set your combo box to some LaF and it breaks the Custom Settings Tile:

So LaF is not usable right now.

[Casey Kolb]

@Lindon Can you post a code snippet (not a HISE snippet) of what you’re doing to the LaF combobox customizations? I customized my comboboxes without any issues to the settings. You might be able to throw an exception for certain comboboxes too.