@Simon Nope, only component values for components that are set to saveInPreset are.

@griffinboy you should set your fictional voice count, assign ids to array indexes and remove them when releasing notes. Then you can check along the array to fill the first empty index with a new od and set event data based on the index.

Your event data for individual voices is in another array, obviously, all ordered by voice order.

@d-healey It no longer crashes HISE :)

I'm using Encrypted expansions

@VirtualVirgin You could try table mode. You might also try using multiple viewports with lists - a bit like how the preset browser is laid out.

@d-healey Ah of course, that works, cheers David!

@Oli-Ullmann obj.text

@hujackus awesome!

bada-bump is there any update on this, didnt find any related commit and messing with it in hise beared no luck, dont know if I missed something or if its still in the works?

@Casmat Nope, you just have to match the shadow colour to the background. Experiment though you might get better results using radial gradients for example.

For more complicated functions you could pass an array of parameters and branch to different functions based on the length of the array.

For example

inline function myFunc(params: Array) { switch (params.length) { case 0: return subFunc0(); case 1: return subFunc1(params[0]); case 2: return subFunc2(params[0], params[1]); case 3: return subFunc3(params[0], params[1], params[2]); } }

@Lindon of course it is, thankyou.
I think I tried that with intensity and had to do it the way I posted for it to work so I just went straight to that for inverting.
Need to stop asking questions at 11pm when I’ve been going since dawn.
Thanks

@d-healey said in How to use Modulator.exists?:

Did you try it? I get an error.

That's very interesting. I spent so much time in the C++ i failed to consider if it even compiles in HISE. I assumed it did, but it doesn't in the onInit() callback. It will compile if you call exists() in any of the other callbacks, but will throw an error at runtime.

Perhaps exists() is not supposed to be visible in the API and was accidentally added into the documentation?

@d-healey Thank you!

@aaronventure My dude - thank you! This is fantastic…truly appreciate the detail. This is all new to me and incredibly helpful—cheers!

Great, thanks a lot, guys!

@d-healey Thankyou, I had it in my head that the processor id wasn’t in the inspector for slider packs.
Facepalm.
Thanks as always

Done - https://github.com/christophhart/HISE/pull/680

I'm reviving this topic because I'm facing the same issue.
(Tested in multiple DAWs, on Mac and PC - develop latest commit)

After loading the plugin in a blank project: the tile is correctly displayed.
When loading a saved project in the DAW - without quitting and reloading the DAW : the tile disappears
When quitting and reloading the DAW, and reloading the saved project : the tile is correctly displayed.

I'm using a MidiOverlayPanel to allow the user to drag MIDI into the DAW.

The floating tile follows the mouse when a user hovers over the MIDI files (painted in a panel). When doing so, the panel loads the corresponding MIDI file in the MIDI file player during the mouse CB, so when the user clicks the tile, he can drag it into the DAW.

8375bbf5-6fd8-4338-a44f-010a71ab4486-image.png

I'm explaining all this because I made a function to track what the tile is doing.
The tile is still there, placed where it should be, and the MIDI files are correctly loaded into the MIDI player (so no problem here). If I hover where the tile should be, I can see that the panel is no longer hovered - so there's something invisible there - but it's impossible to click and drag the tile. So the tile is still there but I can't interact with it.

@Christoph-Hart it seems to be not related to what I'm doing with the MidiOverlayPanel floating tile, so the snippet above can be used to reproduce the issue.