@ustk ahh. makes sense. Thank you.

bump bump - need mouse scroll callback on panels

Solved, HISE_BACKEND_AS_FX was disabled by default in the plugin version of the Jucer. Shouldn't be...

@David-Healey I have not sorry, gonna spend all 5 hours on this. Thanks!

@David-Healey Ok , thanks

@Soundavid Yeah presets are limited to the factory until the expansion is loaded if I remember correctly. I have a series of open PRs that add more functionality for working with expansions.

de206c4c-9848-4035-b756-9a2843fa229c-image.png

@TalesOfAudio Press F1 in HISE to view it offline - needs to be downloaded first time.

@David-Healey I have tried it on the latest commit but the problem is still there.

@Christoph-Hart I think not. As this is showing up in HISE as well as compiled plugins.... see my posts at the start about using Console.print to tell me whats happening...

Sent you the project link to your email

@ulrik of course. Git is the single tool across all software development that pays off. I couldn‘t imagine doing any non toy project without version control. How are you tracking your progress?

@David-Healey yep great, and dumping the quarantine worked for me so thanks.

@Christoph-Hart not that I'm aware of, I didn't even know this macro 🤷♂
I checked and it's 8 as it should...

@ulrik sure

I had Claude give it a go. I also noticed that the linear-slider class is added to knobs, even though they're not linear.

Also made it available in laf and added getStyleSheetProperty too

https://github.com/christophhart/HISE/pull/935

@boim98208 For some reason this was only happening when I did learn midi CC. I decided to just stick with a set CC channel for the knob to be better safe than sorry.

@David-Healey Ahh cheers dude. Yeah I get it now. So I've done this for my factory content and it worked fine. I need to figure out expansion packs, but I would guess it is a similar approach; making sure my expansion pack installers put the files in the correct place, and having the plugin scan on startup.

@David-Healey Thanks David

Also, worth remembering... a compiled plugin CANNOT use the builder - at least for the most part. So what I've also got is a PluginStateData namespace, which maintains a key:value dictionary of module id's to module references. This runs on plugin instantiation, retrieves all of the actual object references, and stores them in a const dictionary.

You should only use the builder to build the module tree. You should not use it for retrieving or storing id's or object references.

@David-Healey That did it! I updated to the latest develop branch and multi-file drag/drop istarted working immediately. Thank you much.