@Chazrox Thanks!!

Actually the support for custom fonts was already there in CSS for the multipage dialog, but I haven't added it to the script components yet, but now it should work.

Note that you have to use a @font-face at rule that defines the custom font like this (this is somewhat standard compliant):

const var laf = Content.createLocalLookAndFeel(); laf.setInlineStyleSheet(" @font-face { font-family: FunkyFont; src: url({PROJECT_FOLDER}Fonts/DigitalNormal.ttf); } button { font-family: FunkyFont; } "); Content.getComponent("Button1").setLocalLookAndFeel(laf); const var Label1 = Content.getComponent("Label1"); Label1.set("fontName", "FunkyFont");

@d-healey Thank you, i will try that

@Chazrox 😁

@d-healey
80008192-4bd4-44ac-9160-83b0f3e0e99c-image.png
lol

@rava2212 it works thanks a lot

@ILIAM said in Random Button & Radio Buttons?:

David, is this Correct now?

I don't know, if it does what you want then it is...

Buttons[i].setValue(i == random ? 1 : 0);

i == random will either be 1 or 0 already, so no need for the ternary operator here.

@Chazrox Yup, watch my file and file system api video

@HISEnberg Gnarrly 🔥

@d-healey said in Display output levels.:

@Lindon you can with laf

oh of course, silly me...

@Oli-Ullmann Just looked, wow that is massively helpful!! Thanks!

@d-healey wow. lol. Thanks!

@VirtualVirgin yeah once in on init is good

@d-healey I'll read this for sure. Thank you.

@d-healey Wonderful I'll see if I can rewrite with just the File (System) APIs in that case! Luckily for me these are "universal settings" so they should be applied cross each instance of the plugin.

@VirtualVirgin

You shouldn't declare a function within a paint routine or mouse callback. I'm pretty sure that will reallocate memory for every redraw of the screen or mouse movement.

Functions should be declared in on init, and 99% of the time they should be inline functions.

For paint routines and the like for your factory functions, I would declare them outside of the factory function - unless they're really short. This is more of a code cleanliness thing though than a performance issue.

local t = Engine.createTimerObject(); t.setTimerCallback(function[panel, t, rangeMinMaxArray]

Why don't you use the panel's built in timer instead of using a separate timer object?

@d-healey Wow...

ok. Thats way easier. I wish I would have known this a few hours ago. lol eh.

Thanks!
(for the next one)
Screenshot 2025-05-11 at 2.39.49 AM.png

@griffinboy yes it copies the data so that it works across the DLL boundary of the network DLL (otherwise it would be very prone to crashes). Once it's in HISE it will be referenced (so if you attach multiple callbacks they will use the same data object).