@d-healey This is not something that implemented, yet. Script panel mouse wheel callback still not implemented. (Checked the sourcecodes as well on github, latest branch) Although, it is detected by JUCE, but the event could not be catched as there is no event.wheelup or wheeldown or anything like that. An EQ contains scrollwheel callback indeed, just like the knobs, but other components like images or panels are not. Panels should have this feature.

I'm also looking for some workaround for detecting if the mouse wheel scrolled up or down under a specific Panel widget.

@d-healey @Christoph-Hart - any idea how to achieve this?

@oskarsh Another friendly bump.

I want to use it to move panels down/up.

@ustk I believe it's Synth.noteOff() that's deprecated. If you use it, the console throws a message to use noteOffByEventId. Anway, I only used playNote hoping somehow it wouldn't require a noteOff callback as I was testing @aaronventure suggestion.

I think it would be better to just add the octave control to the existing qwerty keyboard function. :crossed_fingers:

@Lindon said in .getItemtext() on Viewports:

it would be nice if (like ComboBoxes) we had .getItemText() on viewports...

and on panels 👍

@Orvillain if you put it into scriptnode it would.

Pretty sure you could just do it with code in the processBlock (it's undocumented; print the channel obj to see what you can access) by referring to a global array where you set the gain and pan data.

But it will definitely work in scriptnode. Maybe you can just do a gain node and a clone node, then access each gain's parameters directly without creating 94nnetwork parameters and connecting them, but Chris is sitting on the API as its unfinished so you'd have to ask him.

If each of these is a separate voice, it's more efficient to do a gain modulator and just set the gain and pan in on voice start by adding a script voice start modulator.

Then you can just send the gain and pan data with the new globalcable methods alongside the note id (even though sending 0 doesn't work in scriptnode at the moment).

@Christoph-Hart Any chance this can make it to other drop shadow methods soon? I'm profiling my UI right now and the hungriest call is by far drawDropShadowFromAlpha. Using one of the two blur options is a few times worse.

Btw the Perfetto implementation gets me all hot and bothered!

Also I just realised that the contents of the note floating tile is saved with HISE not with the project, this seems pretty useless. I think project notes should be saved alongside the project, I can't see why you'd want a note across all projects.

@Christoph-Hart I dowloaded the latest Hise develop and it solved the problem, I can export now

This is still broken because 0 cannot be sent:

https://github.com/christophhart/HISE/issues/537

@Dan-Korneff nice. Well done.

@d-healey opengl is still supported on macOS but there‘s no guarantee on how long this will be the case.

Textures cannot be loaded to the shader because the shaders in HISE are fragment shaders and you need vertex shaders for this, but you can pass around a buffer as uniform data and visualize it in the fragment shader.

@HISEnberg yes, good idea, that also crossed my mind at some point.

@Christoph-Hart Sure, I'm motivated. Cheers.

@Christoph-Hart I mean why not, although that requires management of the input min and max values, so you can't easily plug any input toggle in there.

Why not both? You'd just have to make the unscaled version of minmax 😄

I don't think there's such thing as enough nodes

I'm in need of this as well.
Looks like there's a solution here:
https://github.com/FigBug/Gin/tree/master/modules/gin_webp

Might give it a try this weekend.

@d-healey yeah, I've pushed the example snippet that replicates the behaviour.

https://docs.hise.dev/tutorials/modules/index.html

Not sure if that is a good example for an introduction to broadcasters though as it's a little bit more complex than just a hello world example that listens to a single event - there are two broadcasters and one is changing the source event of the other.

@Christoph-Hart I have a suggestion to further improve this.

the "from..." label should also include the parent node of the source. It already does if it's the parameter, but not so if it's a node.

E.g. CompChain.ramp.

It should include all parent nodes as well, which will make navigation easier for larger networks. But it should only include the parent nodes that are different from the parent nodes of the target.

So if they're both wrapped in the same framex node, that wouldn't get mentioned. But if they're in two different chains which are inside the same framex node, framex doesn't get mentioned but the chains do.