@goldee Yes you can do this with HISE

@Morphoice if you want a more detailed error message try opening the generated AutogeneratedProject.jucer file from the DSP Networks Binaries Folder.

You can then compile this file as you would compile HISE in VSCode or XCode. This usually yields the correct error message.

@griffinboy i suspect that implementation will just be a stretching of the path across a different area, haha.

For multiple channels, you'll probably find it easier to do using the new Rectangle() object.

@d-healey Amazing! Thanks :) I posted this before realizing they didn't work in expansions. But maybe that can be fixed

Free mankini with every commercial license???

@aaronventure It shouldn't be limited to 16, but there's still a bug with the number of sliders an ExternalSliderPack can handle.
This might be of interest to you: https://forum.hise.audio/topic/11411/externaldata-sliderpack-seems-to-be-limited-to-128/13?_=1743103883757

@aaronventure I requested a proper bug tracker a couple of times, something like Mantis. It would prevent bugs being lost in the ether of the forum, or being lonely on github.

@Christoph-Hart Nice, going to give this a try now.

@clevername27 said in [feature request] Stop specific broadcasters firing at on init:
It's also not always possible to tell if a broadcaster is being called at startup…which doesn't sound right, but there are edge-cases.

Can you make an example?

@d-healey

Proposes the feature. Documents the feature. Codes the feature.

Because that's how @d-healey rolls.

@Chazrox Did you try itemColour1? You can use Console.print(trace(obj)) to see what's available.

Krita is open source and C++, the answer might be there somewhere, surely the colour picker logic could be tinkered with. Not that I would know

@ustk Wow seriously impressive work here! Excited to dig into this.

@d-healey This is the only mention of "linter" on the forum so far :D

I know nothing about how much effort implementing a linter would be, but even the low hanging fruit would save me a lot of development time. Yesterday I spent ages debugging a condition where I accidentally went if (var = 2) instead of if (var == 2).

I assume the ideal solution would be to adapt an existing linter, but maybe there's an easy way to do some basic checks until then?

Hence the feature request :-) fadeComponent has been working very well for me so far, it would just be great to have a quick and easy way to achieve fades to semi-transparent states like this.