@VirtualVirgin define an inline function with a g argument, write it and then just pass the function into the setPaintRoutine method call for any panel you want to use it for.

@d-healey Thanks!

@clevername27 said in UI Factory Method:

@VirtualVirgin If you search the forum, I wrote a detailed tutorial on using UI factories, along with example code.

Thank you :)
I'll take a look.

@VirtualVirgin said in How do I actually get the return from splitCamelCase?:

this is all pretty new to me

You're doing great :)

@VirtualVirgin said in Trying to make a factory method but getting an error:

Looks so obvious when you point it out!

Yep, but it still took me at least 30 minutes to figure out what was going on.

@ulrik said in I am trying to get the position of the component that is being hovered over by the mouse to no avail:

@VirtualVirgin it's Content.getComponent("ScriptLabel1"), you forgot the "Content"

Sorry, I was trying to use the function you provided:

// get the component object inline function getComponent(componentId) { for (c in AllComponents) if (c.get("id") == componentId) { return c; break; } }

@d-healey
Thanks! I got it working from your snippet.
The preset browser now resizes nicely if I change the interface size.

@ustk said in Is there a way to get the bounds of the front interface?:

@VirtualVirgin Yeah like Dave, I always start my interface script this way:

const var INTERFACE_WIDTH = 1000; const var INTERFACE_HEIGHT = 623; Content.makeFrontInterface(INTERFACE_WIDTH, INTERFACE_HEIGHT);

So this can be used everywhere

Thanks :) I just added this and it does what I needed.

@DabDab said in I'm having issues converting an SVG:

@ustk Thank you. Got the fundamentals. one last question. How can I do tracking circle?. Increase /decrease just like regular knobman things.

With

Content.createPath()

and

Path.addArc(var area, var fromRadians, var toRadians)

Multiply your arc endpoint (var toRadians) by obj.valueNormalized.

@ustk said in How can I improve the tracking when using LAF on a slider?:

Forgot to mention that mouseSensitivity is working only for rotary sliders, so just change that and the LAF function and it'll work

Thanks :)
I changed the LAF and the component over to rotary/knob and now the mouseSensitivity does work.
Setting it to 0.35 seems to do the job.

@VirtualVirgin

Nevermind! I got it.
I have to delete all of the original header panel before importing the new one.

@VirtualVirgin said in Using "obj":

I was referring to the difference between the user name for the ID and the one HISE creates "Object 0x58dca420" or whatever it comes up with.

Console.print will only display text. When you pass it something that isn't text it will display what it is, Object, Array, etc. In the case of objects it also prints some hex numbers which I'm not entirely sure what they are, perhaps a memory address, either way the information is not useful to us.

d6c2f95c-c442-4e86-b8fd-ca466ccca12f-image.png

@VirtualVirgin https://forum.hise.audio//post/89104

yes that's a known issue. Unfortunately solving it means that the code tokenizer would have to scan the entire file to grab the correct colours which comes with a huge performance hit on large files. It's obviously possible to solve that, but not super trivial.

@VirtualVirgin said in What are these values in the Script Watch Interface for the onNoteOn and onNoteOff callbacks?:

These will increase with more code

It depends on the code, you could write a few lines of very inefficient code that's would greatly increase it, or many lines of efficient code that would affect it much.

Also it's not such an important value in a GUI script, but on a real-time script it could be very important.

@d-healey said in How do I transfer from the main interface script processor to another script processor?:

@VirtualVirgin You can't, you need to separate functionality from UI. So in your secondary script you can have all the keyboard functionality that you want, but it doesn't matter what it looks like, so you don't have to use the same UI that are using on the front end, but you can if you want. Often a good choice when there is lots of data is to use a sliderpack. Then on your UI script you connect the controls to the secondary script, just like with the built in HISE modules.

If you want separate your keyboard script into a separate script for organisational purposes, you should put the code into a namespace, and put the entire namespace into a separate js file that you can "include" in on init.

I've been looking at the namespace into .js and made a few earlier and getting a grasp.

The reason I am moving the keyboard to the container though is that I need multiple keyboards representing multiple stages of MIDI signal flow, so picture an input keyboard, a transformation keyboard (showing what you are doing in an intermediary stage), and a post-transformation output keyboard. I figure the easiest way to route those stages is the subsequent keyboards just pick up the incoming notes at that stage, because it sees any generated MIDI as new callback inputs.

One reason for making my own keyboard in the first place is that the built-in one is hard-coded to the MIDI inputs, and when you add it to subsequent stages (of script processors), it still reads directly from the inputs selected in the "MIDI In" of the project settings, and not the input of just that stage.

@d-healey said in Am I supposed to be using local or var for LAF functions?:

@VirtualVirgin var

Thanks :)

@d-healey Hah, as I said. Thanks!

@VirtualVirgin Cool, thanks for checking. I tested in HISE too and it's the same. I'm updating my PR now.