@d-healey said in Tooltips for Disabled Components? (To Tell Users WHY a Widget Isn't Available):

I remember reading that today Imugur is having a purge of all the porn on its servers, so that's probably affecting your dirty HISE pictures :)

😂

@ulrik Thanks again for your keen eye - I've replaced the snippet (again, lol). Cheers.

@audiolyf It's not something I've explored.

@d-healey Looks cool 😎

@iamlamprey just three keystrokes.

@ulrik i started a new thread for this. perhaps you could take a look at the snippet ive shared there and let me know if im on the right track- https://forum.hise.audio/topic/7530/midi-player-drop-panel/4

@ABYSS_CO said in Use tags:

@Lindon Thanks for the informations! I will try. And is it possible to add tag scripts in an expansion? With additional scripts? Because this method only works for the presets included in the standard version, no for future presets.

see point 1 from my (admittedly brief) explanation - you could easily add a preset tag meta data file for each expansion you ship...

@Dan-Korneff said in Panel "isPluginParameter"?:

I'm using a panel for buttons. Would like to automate them.

Indeed, is it possible to make this work @Christoph-Hart ?

yep compiles successfully, thanks again :)

thank you for the tips!

@Lindon cool, so much better. Much appreciated!

@clevername27 Wait, you were right - the answer is to simply store the states of the child modules. (Specifically, just use constant modulators, and restore those states.)

@d-healey I don't care if you are using HISE to make "virtual instruments" (as if that's a real thing). You're alright.

@Lindon Yes :)

@clevername27 I've uncovered the answers—for the interested;

To draw a specific section of the waveform, use a Viewport, and put the waveform component inside—from there you can scroll and zoom it. All these factors are floats from 0.0 to 1.0; so, to show specific parts of the waveform, simply divide 1 by the sample length (in whatever units you want to use.) The green line is where the sample begins playing from. If you've used the sample start offset, the green bar will reflect that. The translucent areas on either side of the bar don't mean anything—they are there to make the green bar stand out more. So, the active sample start is drawn automatically; if you want to hide it, then make it transparent. To do that, you need to change its colour, which is done in SampleDisplayComponent.cpp:

Screenshot 2023-04-17 at 1.12.09 PM.png

(And of course we can also simply change the colour to match your palette.)

Screenshot 2023-04-17 at 1.14.43 PM.png

Apparent bugs (noted here and elsewhere on the forum):

LAF: Some of the overrides work; some don't. (You won't get an error message; simply nothing changes.) However, there's a lot of flexibility built into the default look and feel, and the most important one (drawThumbnailRange) does work, and you can choose only to override specific drawing routines—the others will use the default ones via the Property Inspector. The playback head (white) sometimes freezes when another note is played.

@clevername27 Here's the API call:

Engine.clearUndoHistory();