@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 I haven't - isn't it limited to like 16 ? I need around 200 parameters for this one network.

It's loaded with Faust stuff so if you can tackle the Faust compilation issues, it may be that this network doesn't need to be compiled so this method can be used, as it would barely benefit from it due to how much of it all is Faust.

More about that on the appropriate thread, which I'll update as this has given me an idea...

https://forum.hise.audio//post/100190

@Christoph-Hart

Can we get something like this please?

@Christoph-Hart I'm not seeing it

Edit: Ah I think I need to build with some newer commits, but that webview stuff is still enabled and giving me build errors.

@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

@Phelan-Kane this issue still seem to exist. Often also the compiler log gets cut off in HISE so you actually cannot see the error output.

@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.