Don't use it, it's bad and will be gone very soon.

yeah, the attempt of wrapping up the mod matrix lead to 5 people having 20 different requests for their individual projects. Maybe we need to settle on a common denominator feature set and make this robust - that's what this system was designed for.

@DanH you‘re using an outdated projucer build - it can‘t parse the vs2026 config. Make sure you use the latest one from the repo

this function is only available for a Table, not for a ScriptTable.

yes HISE, good HISE.

@David-Healey I don't think it's a regression, if it happens to CUBE then it has always happened - I'm fairly confident they are not using the latest HISE version for their current version.

@HISEnberg ah ok and it‘s still happening on the current dev branch? The cube plugin is quite old so it might be fixed in the meantime.

@Straticah Can you try to make a minimal example that crashes FL Studio? You can start with the webview examples in the hise_tutorial.

Ripping out the webview for your preset browser would be the wrong move, let's see if we can fix that.

@DanH raw output from the broadcaster wizard works:

// Broadcaster definition
const var asd = Engine.createBroadcaster({
  "id": "asd",
  "args": ["processor", "index", "value"],
  "tags": []
});

// attach to event Type
asd.attachToComplexData("Table.Content", ["LFO Modulator1"], "0", "");

// attach first listener
asd.addListener(0, "set content", function(processor, index, value){
	Console.print(value);
});

@Oli-Ullmann weird looks like a regression and it only happens if you replay the same note. I‘ll take a look later.

I'm pretty sure HISE has shown up at some point on Audioz.net with a rapidshare download link. Fun times back then, no looming AI apocalypse, just good ol' copyright theft by script kiddies.

@inlandempire same reply still applies, please upload one sample with the looppoints and if they don‘t work I‘ll take a look.

@DanH I need to check, not sure if it's on develop too - it might be possible that it's only on my private feature/ai_tooling branch, but I'll probably make that public soon anyways.

I've got a set of guideline files that teach the AI agent how to write code that matches the codebase and it works pretty well.

@DanH ah ok, well that's precisely the difference between "lol AI cannot do s***" and "boy we're f***ed"....

@DanH said in New LAF Properties for Modulation Display: Selected Source vs Accumulated Range:

it doesn't have access to the whole codebase but it

Lol why? that's the first thing you need to do, start the claude session from the HISE repo folder, it will then just explore and pull in whatever it takes. A full codebase exploration including the fix of this scope should stay below 60k tokens.

@DanH Just looked at it and I'm a bit disappointed - the code quality is far worse than what I'm able to oneshot without any guidance with my tuned workflow. I'm afraid we have to postpone this until the procedure is ready.

If it fixes your immediate problem, then just take the fix and use it locally, but I would have to fully rewrite every single line of code to match the coding style / structure and quality of the existing code.

@DanH one level higher is a hack and just solves your immediate problem. If the parent component one level higher happens to cause clipping we're back at square one. Sounds like One More Lane Bro to me...

@DanH This is exactly the workflow & scope of fix that should be covered by the new contribution workflow, so I think it would be best to get you up and running there ASAP.

For now just make a manual pull request with the changes, I'll review it and merge if OK.

Oh, but this style sheet should correctly assign the label selector to the outer UI component - I assume you don't use it with nested UI components? Can you make a minimal example?

@dannytaurus well actually I can just append an empty selector to each style sheet collection internally by default, that would remove the entire problem for the user.

Yes I cleaned up a lot of CSS issues, I think one of them was a bug where a internal component id #controller overwrote the ID selector that should be reserved to the UI component ID. That should always take precedence

Just change #controller to #FloatingTile1 in your code. Note that I'm not applying the same level of strictness to CSS backwards compatibility like to the rest of the HISE codebase so you might encounter a few other glitches.