no worries. getAllComponents() has a single parameter with a clear purpose, so it's not comparable to the function you suggested though.

@d-healey yeah I came about the other way around: I used only repaintImmediately and realized my sliders weren't updating. I didn't think to try sendRepaintMessage for the panel.

As for the speed, I meant mostly in comparison to sliders and buttons that use LLAF; larger animations are much smoother with the panel and its paint routine.

Nobody forces you to use the range defined by the knob in the module editor.

HiseSnippet 1216.3oc0W0raaaDDdokXZkcqQcpQQOxC8fCZPfUiqaK5AKaYKCgXYKXpjVfbHXM4PoEd4trKW5Zkfdq8bdSBPeBZeD5qPO2K4MncVRJIxDYaYAm5Vdff6r6ry2N627C6pjdPbrTQrp0aXDPr9.a2gB8flCnLAo8tDqks6Pi0fxISzNCinwwfOwxpx9FAV0pRRed8V6P4TgGLQDg7DIyCNfExzSj1swiXbdKpOziEVX0aznsmTzTxkIHdpXuNIh5cJsObH0rrErIV2YOelVpb0TMDSrptizen6.4OJxV+SXwrS3fYPchKtQYhaI49FDajRZNfw86N5bGSHV1cm3Epj4EV0tCymMV9DuwGkNgyDMJ5OrVnL7pTBd0uH3MEHYU.RUyfzJ1tdJVjdxLF7rjcaAd4DPQ2dQnjsVh0ua2ThKPnePH8TnkBGLVg01b80uuC95deaPhvSyjBGo3PoFNRr18V7EKVaweZQm2bpffoNmwLJImCpoNs4lVcYJtlHI7DPcemyn7DX7BwieYe5clMepW1otvBkh1Bl9nHHe7kSJH4tMycQNBwkpSuIVN+lvky7AEggax6Y+Hg7j5jTvmync9k+5W2h7316R0zQaCtinUh.klYNLV6BmgwGYWv0r2EhOUKiRWaXjTXru0xWoQOGovVuBs3PyGuD+HVOz3RtS5BHgLeeNzUFyLt7BAr+FFWG4xddJhewpuZ++74+7VgEioIjP54ECwiSBBXmmFLFv3gwZDSsCwXTh0csebL33CAzDt1I9Tbe3LwofeOY55iF4da6ahiNn0QNcj9IbJd6VGC0UXTNxLMytjcKE7CIfvaHlt3sBEvfvQJVLxzjNJeBy4rX3fgyKvy+vhmkqQ355WZ35rBwUr6xzdClNFWXJXDoMuKvXdRtOzduf.vSOAfUsa88yaFsY27KmY9krcYBHsZSpw+jzwNeG8LvYeP.pLhwEWv4Ol0BNQybAmi7zn46onh3HYboM1EBY8vXx3hBQFugodr41rn7lRpZpS85sZgGxopiKUmnRoEaGJSD5RzfJWVguKLKX4HhBqeJkbpdKTE7lIr5VLxuTg5ZivnKKLhC6INC3Xt9TLdWL4dZhwQRKSr6HExnARAyq3s9w.ldseePUD6S8.ssVisJMQxpMNF3.sHC9yZb.x7nJzOAyou352zxTuu9T6L35XhFc9+aF6JuayXWxetRFHsMkMyI8uQAzqz4sCKRxoJSolIUWKzphI+X6IoWa7xFlTwARUXd+Ii2oCf9nMKJoGf8qfoxKQecCkR8.lne4rtq13.oLZOAE8B9E2jtCPBK1eYLTJ2mYa6Iy9IjlbYQZNgztuPpfrdVKk.NIVKCGc.R6+vEa1IsWLqmZu4FO.eB9by6uoI95gGcyLlbyENsvLxQ+3Tlv3qbCm35GIUc1XoWQSyWKDOlD9eDDeazUzwxDMFfzghI5MsweXRnK1LhGfVWH.droi9EL74rwqaFm0MhvOcveiO4SV2L1Jex5il7eEaDR8Txm4k8iRFx66mJAO2hz+culcGyXmx+gT1OXfcR7LOuxa0ao3WLuJ9v4UwMlWE+x4UwMmWE+p4Uwu9pUzzn21IXtzrxeDRmt6kkE0ZbJbqJj+ANWQ2eC

@GUJIAN The expansions video is a different one. This one is for the categories column, I also did one for the bank column.

https://forum.hise.audio/topic/8782/scriptnode-filter-node-with-filter-order

@Orvillain Spoke too soon. From a fresh instance on Windows, it crashes. Haven't tried MacOS again.

@Christoph-Hart Hehe I didn't know that. It's not that important, but perhaps a consideration for a future version of Hise :)

@aaronventure That's too much context required for the autocomplete, so I'd rather put this in the Broadcaster Wizard's list of things.

@clevername27 lol

@aaronventure Yeah thanks, I know PluginDoctor but that's more about the project needs indeed

I'll make the first donation.

Thanks @d-healey and @Christoph-Hart - good to know.

I should have clarified in the feature request that, of course, one would want to be able to edit the prefab modules in the interface designer, for those of us who just want to quickly prototype visually without doing a lot of coding. But, if that is impossible, then, yeah, not worth it.

Anyway, thanks again!

@gorangrooves said in HISE 4.0 - Wish List - Add yours.:

Please make HISE fully compatible with screen readers before adding new fancy features or releasing v4, so that blind users can properly use our existing software.

Yes, please
I've been trying to do this also, please make this possible.
I heard about the NVDA screen reader, but the NVDA scripting doc is out-of-date I guess.

@wellplacedmusic Yeah it's not that discoverable I guess. It's been there since the earliest versions of HISE so I'm used to it but perhaps a little left click menu icon would help people find it instead of it being in a right click context menu.

@Natan the variable in the first argument on Line 26 is not defined yet.

@DabDab That's too bad. It's really annoying. The closest thing to a fix that I could come up with is to add a really long .fadeComponent on the noteOff callback. It can give the impression of being always on. But not really, and it doesn't come without other issues. Hopefully Mr Hart adds a fix.