Output the value of a slider in a separate label

[nic]

My problem: I want the functionality of a slider/knob but it should just show it's value and nothing else.

So I set up a slider with a blank png for filmStripImage and output it's value in a label via setControlCallback(). It works, but when I connect the slider to proccessorId and parameterId the callback is not called anymore. What can I do to solve my problem? Or is there a better approach? Setting up a blank png feels not right ... can I just delete the look and feel? How? And how can I manipulate the value so it works in ms but outputs it in percentage?

[d.healey]

@nic Use Look and feel to get the appearance you want. You can't have a callback and parameter/processor ID, it's one or the other.

[ThomAce]

@nic

You can do a callback.

For example:

1.- Drop your slider name the component as MySlider1 (just for staying at this example)
2.- Drop your Label and name it as MySliderValueLabel
3.- Go to Interface oninit script and add this to your code.

Content.getComponent("MySlider1").setControlCallback(onMySlider1);

inline function onMySlider1(component, value)
{
	Content.getComponent("MySliderValueLabel").set("text", Engine.doubleToString(value, 0));
}

[d.healey]

@ThomAce said in Output the value of a slider in a separate label:

Content.getComponent("MySliderValueLabel").set("text", En

Avoid calling getComponent from within a callback, instead get the reference during on init and store it in a variable that you can refer to from the callback.

[ThomAce]

@d-healey Is there any good reason for that? I know, JS is a bit dumb and quasy-OO language. But, what is the reason behind to make a global reference of the object at initialization (wasting memory) and referring to that instead of calling it when it is needed? Javascripts superslow memory accessing/addressing?

[d.healey]

@ThomAce Performance boost for declaring widgets as a const (in fact anything you can declare as a const should be) - https://forum.hise.audio/topic/79/scripting-best-practices

[ThomAce]

@d-healey Thanks for pointing out that. You might have some good idea for my question that I raised not a long ago. Would you mind to take a look at that as well?

[nic]

@ThomAce I had this but when I link the slider via processorId it doesn‘t fire the callback anymore.

[d.healey]

@nic You can use either processor/parameter ID or a callback, you can't use both at the same time.

[nic]

@d-healey thanks, yes I will try this way. Do you know code examples for lookAndFeel? I really don‘t know how to start. How to set up my own look and feel for the slider would be enough.

[d.healey]

@nic said in Output the value of a slider in a separate label:

Do you know code examples for lookAndFeel

What do you want the LAF to do? I have a few videos demonstrating different things you can do with it.

[ThomAce]

@nic You can use only one way as d.haley already mentioned that above... If you configure your slider in gui designer to Parameter Properties, and at the same time you set up the callback in oninit part of the code, you will lose controlling.

const var MySliderValueLabel = Content.getComponent("MySliderValueLabel");
const var ControlThis = Synth.getEffect("YourScriptFX or whatever you wanna control");

Content.getComponent("MySlider1").setControlCallback(onMySlider1);

inline function onMySlider1(component, value)
{
	MySliderValueLabel.set("text", Engine.doubleToString(value, 0));
	ControlThis.setAttribute(1, value);
}

Also, at the bottom right corner of the code editor, there is a Compile button. You should use it quiet often if you write codes...

I still need to used to this tool as none of RDEs worked in this way I used (Delphi, Lazarus, VS, so many Java and C++ developer environments...) But, it is still more userfriendly than Java developer tools.

[d.healey]

@ThomAce said in Output the value of a slider in a separate label:

Also, at the bottom right corner of the code editor, there is a Compile button.

Shortcut key F5 will save you some clicks

[ThomAce]

@d-healey Yeah, but you know how we develop... :D Typing something, then CTRL+S, CTRL+S, CTRL+S... But good thing anyway to use the F5... I didn't knew that this works on code editor as well. A visual feedback might be helpful for such idiots like me. :) I always forget that the code not in sync with the gui design. But, despite some bugs I found in the tool, it is awesome.

[nic]

@d-healey I just want to output the value. So basically like this:

CUTOFF: 100%

And when I drag over the number or use scroll wheel it should increase/decrease it. In other words, the behavior of a diagonal slider but it should be not visible except it‘s value/textbox.

[d.healey]

@nic In the look and feel function you just need to draw the text then.

[nic]

@d-healey can you point me in the right direction how to set up the laf function? I have Content.getComponent() and don‘t know how to assign or start the laf.

[Mighty23]

@nic

const var Label = Content.getComponent("Label");
const var Knob = Content.getComponent("Knob");

inline function onKnobControl(component, value)
{
   Label.set("text",value);
};
Content.getComponent("Knob").setControlCallback(onKnobControl);

If you want something more "fancy" perhaps you could consider making only the writing visible on the label and making the other customizations in a panel. From what I understand it should be the most immediate way.

Values ​​and strings in labels can also be concatenated with the "+" symbol

.set("text", Engine.doubleToString(value, 0)+" %");

[nic]

@Mighty23 thank you very much but I already tried that. The problem is that I want to use proccessorId and so setControlCallback() will not fire. I have to change look and feel instead.

[nic]

If I do this:

const var cutoffSlider = Content.getComponent('cutoffSlider');
cutoffSlider.createLocalLookAndFeel();

I get error "function not found". How do I set up it correctly?