@d-healey it's my understanding that logic and pro tools support mono to stereo where a mono track becomes a stereo track at the insert point where the user inserts an m>s plugin.

this plugin does not make sense to run as mono > mono.

Yes to both. There is a lot. I'm currently going through the process of commenting things out and making test versions to see if I can make one that works.

@d-healey Yes. I do have a high dpi mouse and now you’ve given me something else to worry about and have to test for. I did not think that dpi could be a factor.

Based on what I figured out rooting around the Hise source it seems like all sliders in Hise are set to absolute px mode as default with a value of 250 distance = full rotation. But when you turn on the modifier they switch to a velocity mode. The problem I had is that the velocity mode settings weren’t any good (at least for my mouse) specifically the offset aka minimum.

JUCE: Slider Class Reference

(docs.juce.com)

I found a setting that makes things much smoother and more predictable. But I guess I have to test with different mice?? Oh joy.

Where can I change the compile options that Hise uses when compiling faust nodes?

I can open the .cpp file generated by Hise for my faust dsp and it has the compile options Hise used commented out at the top, but I don't know where in Hise I can edit those.

As an example I would like to use double precision floats. Hise is currently set to use single.

@aaronventure thanks!

I had actually just figured out on my own how to do this with a gain module directly. But your version in scriptnode is better.

@Christoph-Hart thanks for tackling this issue so quickly!

Tested as working on my end.

@d-healey said in [Feature request] Missing Laf colour properties:

• drawPopupMenuBackground, use the combo box colour properties (would also be good if the base colour was transparent so we could do rounded corners, currently it's solid white).

This please!

Haha dirty indeed. But it works!

I don't know why but the mouseDownX and mouseDownY values I get when clicking on the panel are always huge. So I'm using an X that's higher than my object width to trigger that? Idk man... haha

if (event.mouseDownX > 26) {
	//click on panel
	//first click shows menu, second hides menu
}

if (!event.hover && !event.mouseDownX) {
	//click off of panel that also hides menu
}

2025 Bump

Is this still missing functionality? I know there is a clear undo list function, but there doesn't seem to be any way of knowing if you're at the beginning or end of the undo list or how many items are in it.

2025 Bump

Is this still missing functionality? I know there is a clear undo list function, but there doesn't seem to be any way of knowing if you're at the beginning or end of the undo list or how many items are in it.

@Christoph-Hart great. thanks!

Is using a path number array more performant or better in some way than using an SVG?

@d-healey great. Thanks!

@d-healey said in Possible to draw beyond callback obj with LAF on slider and button?:

You have to make your control larger. Or draw the contents smaller.

yah... that's what I figured. Kind of a shame. A work around that's very silly but should work fine is to make 2 sliders linked, with one big and one small and disable the big one so it can't take user input but reacts to the value of the small one.

@d-healey I can't tell if the dropshadow on that extends beyond the bounds of the obj.area and it doesn't look like it really changes so it could just be a static background.

What about a glow that glows beyond those obj bounds? It gets clipped and looks bad.

@d-healey I'd like to draw things like shadows and glows and backgrounds that are reactive to the component value and extend beyond the callback area.

@Lindon appreciate this reply. I will give it another go.

With a LAF on a slider or button is it possible to either:

• draw outside of the bounds of the obj.area?
• limit the callback to only function in a specific reduced area?

I can think of a few very unclean workarounds but I'm hoping for something quick and simple instead.

I have 2 sliderpacks and I'm trying to make them match each other. Sliderpacks don't have the "linkedTo" option like knobs or buttons so my hope was to assign the values of one to the other.

I can get the value of any individual slider in the pack with getSliderValueAt(index) but I can't seem to find a way to assign a value to a single slider.

I'm guessing this might be possible using referToData but I haven't been able to figure out how yet.