20 Oct
2014
20 Oct
'14
2:39 a.m.
-------- Forwarded Message --------
Subject: Re: [LAD] How can an LV2 plugin UI get the value of a control
port from the plugin?
Date: Mon, 20 Oct 2014 01:27:10 +0100
From: Philippe Coatmeur <philcm(a)gnu.org>
Organisation: GNU
To: Harry van Haaren <harryhaaren(a)gmail.com>
On 17/10/14 15:56, Harry van Haaren wrote:
On Fri, Oct 17, 2014 at 1:30 PM, Phil CM
<philcm(a)gnu.org
<mailto:philcm@gnu.org>> wrote:
Also each time the UI is opened, the widgets are reset at maximum
(not the values).
Hi Phil,
Glad to see you're excited and working hard on learning LV2! Checkout
the example plugins: they show how things work.
In the UI, there is a port_event() function. It tells the UI what
port changed, and what its current value is. Use this to do
widget->setValue( newValue ); and you're done ;)
For this I had to write my own
int setValue(int value) {
// this->scrollvalue(value);
cout << "Called with value " << value << endl;
}
And it does get called by port_event() now
* what do I put in this setValue() in order to /actually//update/ the
widget value?
There is a int scrollvalue(int pos,int size,int first,int total); in
Fl_Slider.H but can't call it from the class, witch is not explicitely
extending Fl_Slider
<https://bitbucket.org/xaccrocheur/kis/src/8c3a85a9899f117d2fa273b6c7948402d780fb46/widget.h?at=master>
from what I can see... Is it?
Thanks everybody
--Phil
PS - Apparently Sorcer is using AvTK on top of FLTK, I was under the
impression that Sorcer's UI was using NTK, am I mistaking?
Eg (from OpenAV's ArtyFX, Bitta plugin)
https://github.com/harryhaaren/openAV-ArtyFX/blob/master/bitta/gui/ui.cxx#L…
How can I /get/ the control ports values from the UI perspective?
In answer to your Q, how to "get", you don't: you're told when
there's
a new value.
HTH, Cheers, -Harry
--
http://www.openavproductions.com
--
Philippe "xaccrocheur" Coatmeur
http://bitbucket.org/xaccrocheur /https://github.com/xaccrocheur
http://opensimo.org/play/
20 Oct
20 Oct
10:07 a.m.
On Mon, Oct 20, 2014 at 1:39 AM, Philippe Coatmeur <philcm(a)gnu.org> wrote:
<lots of emails>
Hi Philippe,
I can't follow the issue you're having here: you've sent 8 emails, most
with different questions with a layout that is hard to follow: please be
more careful in what text you reply to, and remove all the rest of the
email. Then make sure you're repling to the "linux-audio-dev" list, and not
(only) to the individual.
If you're struggling with code, take a step back, and write a single email,
with a direct question, that sums up what you're trying to learn.
Eg:
How does setValue() work to updated a widgets value in NTK, in the context
of an LV2 plugin?
To which I would answer:
Most NTK widgets that have a "value" like a slider or a dial, derive from a
base class that implements value() and value( float );
What this means for a widget, is that in order to change the value of a
widget called "wid", we do this:
wid->value( 0.0f ); // sets widget value to 0
What you will see here:
https://github.com/harryhaaren/openAV-ArtyFX/blob/master/ui/crusher.h#L156
Is the value() call, which returns the value stored in the base class, aka
0.0f in this case.
To connect an LV2 port to a widget, in port_event() have this type of code:
https://github.com/harryhaaren/openAV-ArtyFX/blob/master/bitta/gui/ui.cxx#L…
Which checks the port number, and assigns the incoming value to the widget,
using the value( float ); call.
Its pretty simple right? Cool.
RE: the other emails, Yes Sorcer uses NTK, NTK is in turn based on FLTK,
and to maintain backwards compatibility with existing code, the function
names weren't changed.
HTH, -Harry
--
http://www.openavproductions.com
1:26 p.m.
Hello Harry;
On 20/10/14 09:07, Harry van Haaren wrote:
Most NTK widgets that have a "value" like a slider or a dial, derive
from a base class that implements value() and value( float );
What this means for a widget, is that in order to change the value of
a widget called "wid", we do this:
wid->value( 0.0f ); // sets widget value to 0
Oh, I get that, believe me. The
info I need is around that ; I wish your
sentence had started earlier, like so "in port_event(), given /this/
class declared like /this/ and an objet wid instantiated like /this/, we
do this (...)"
From my port_event() I point to my UI object via the LV2UIHandle. this
object is a NTK widget (or so I hope, read on). So if I get a:
error: ‘class KisWidget’ has no member named ‘value’ (it's pretty explicit)
It means the class KisWidget has no member named "value" I guess we can
agree on that ;)
It must be that I did not declare my Widget class as a proper NTK
widget. The declaration is at line 25 in this file
<https://bitbucket.org/xaccrocheur/kis/src/8c3a85a9899f117d2fa273b6c7948402d780fb46/widget.h?at=master>.
The instantiation of the widgets (a FL_Dial and 5 FL_Slider) is at line
96 in this file
<https://bitbucket.org/xaccrocheur/kis/src/8c3a85a9899f117d2fa273b6c7948402d780fb46/widget.cpp?at=master>.
Now for the direct questions:
* Is it a proper NTK widget class declaration, that would expose a
value() method?
* Are those proper NTK widget class instances?
Thanks for your patience
--Phil
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--
Philippe "xaccrocheur" Coatmeur
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur
http://opensimo.org/play/
4:36 p.m.
Am 20.10.2014 13:26, schrieb Philippe Coatmeur:
Hello Harry;
On 20/10/14 09:07, Harry van Haaren wrote:
I never use FLTK, but I guess that is something essential.
You need to declare your control widgets in the class KisWidget, not in
the constructor of the class.
in class KisWidget write
Fl_Slider* ReleaseButton;
in the constructor Widget::Widget(void* parentXwindow) write
ReleaseButton = new Fl_Slider( 220,5,35,100,"Rel");
Then you could access the widget pointers in kis_gui.cpp like that
static void port_event(
self->widget->ReleaseButton->value(value);
ReleasButton is a NTK widget, not yourclass KisWidget.
(Just pseudo code here, it isn't exact syntax)
Still, I never use FLTK, I just wonder if you didn't need a
deconstructor to delete the widgets instances which have created with
"new" ( Like you need to do in GTKmm)?
Did FLTK manage the memory?
Most NTK widgets that have a "value" like a slider or a dial, derive
from a base class that implements value() and value( float );
What this means for a widget, is that in order to change the value of
a widget called "wid", we do this:
wid->value( 0.0f ); // sets widget value to 0
Oh, I get that, believe me. The
info I need is around that ; I wish
your sentence had started earlier, like so "in port_event(), given
/this/ class declared like /this/ and an objet wid instantiated like
/this/, we do this (...)"
From my port_event() I point to my UI object via the LV2UIHandle. this
object is a NTK widget (or so I hope, read on). So if I get a:
error: 'class KisWidget' has no member named 'value' (it's pretty
explicit)
It means the class KisWidget has no member named "value" I guess we
can agree on that ;)
It must be that I did not declare my Widget class as a proper NTK
widget. The declaration is at line 25 in this file
<https://bitbucket.org/xaccrocheur/kis/src/8c3a85a9899f117d2fa273b6c7948402d780fb46/widget.h?at=master>.
The instantiation of the widgets (a FL_Dial and 5 FL_Slider) is at
line 96 in this file
<https://bitbucket.org/xaccrocheur/kis/src/8c3a85a9899f117d2fa273b6c7948402d780fb46/widget.cpp?at=master>.
Now for the direct questions:
* Is it a proper NTK widget class declaration, that would expose a
value() method?
* Are those proper NTK widget class instances?
Thanks for your patience
--Phil
21 Oct
21 Oct
11:57 a.m.
On 20/10/14 15:35, hermann meyer wrote:
I never use FLTK, but I guess that is something
essential.
You need to declare your control widgets in the class KisWidget, not
in the constructor of the class.
in class KisWidget write
Fl_Slider* ReleaseButton;
in the constructor Widget::Widget(void* parentXwindow) write
ReleaseButton = new Fl_Slider( 220,5,35,100,"Rel");
Then you could access the widget pointers in kis_gui.cpp like that
static void port_event(
self->widget->ReleaseButton->value(value);
ReleasButton is a NTK widget, not yourclass KisWidget.
(Just pseudo code here, it isn't exact syntax)
Still, I never use FLTK, I just wonder if you didn't need a
deconstructor to delete the widgets instances which have created with
"new" ( Like you need to do in GTKmm)?
Did FLTK manage the memory?
It works :). AND I got one step further understanding
how oop works.
Thank you /very much/ to all of you guys.
--Philippe
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--
Philippe "xaccrocheur" Coatmeur
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur
http://opensimo.org/play/
20 Oct
20 Oct
5:40 p.m.
On Mon, Oct 20, 2014 at 12:26 PM, Philippe Coatmeur <philcm(a)gnu.org> wrote:
Now for the direct questions:
- Is it a proper NTK widget class declaration, that would expose a
value() method?
- Are those proper NTK widget class instances?
You must derive from an NTK widget in order for it to work properly. See
(pseudo)
code:
// derive from slider, to provide
// - value() : to get the current value
// - value(float newVal) : to set a new value
// - redraw() will cause the widget to get repainted at the next
opportunity.
class MyWidget : public Fl_Slider
{
public:
MyWidget( int, int, int, int, const char* ) :
Fl_Slider( ... blah blah ... )
{
// set default value:
value( 0.5 );
}
void draw()
{
// draw stuff based on value() here
line_to( 0, width * value() );
}
// note: there's no *explicit* value() function here, it's inherited from
Fl_Slider.
};
class NtkLv2UI
{
public:
NtkLv2UI()
{
wid = new MyWidget( 10, 10, 200, 25 );
}
MyWidget wid;
};
NtkLv2UI::port_event()
{
if ( portNumber == VOLUME )
{
wid->value( portValue );
wid->redraw();
}
}
Hope that clears things up somewhat, -Harry
PS: Hermann, FLTK / NTK will delete child instances when a window is
deleted. The window itself should be deleted though!
--
http://www.openavproductions.com
1:32 p.m.
On 20/10/14 09:07, Harry van Haaren wrote:
On Mon, Oct 20, 2014 at 1:39 AM, Philippe Coatmeur
<philcm(a)gnu.org
<mailto:philcm@gnu.org>> wrote:
<lots of emails>
Oups, sorry the links point to old commits, please use those :
* kis_gui.cpp
<https://bitbucket.org/xaccrocheur/kis/src/8c3a85a9899f117d2fa273b6c7948402d780fb46/kis_gui.cpp?at=master>
* widget.cpp
<https://bitbucket.org/xaccrocheur/kis/src/8c3a85a9899f117d2fa273b6c7948402d780fb46/widget.cpp?at=master>
* widget.h
<https://bitbucket.org/xaccrocheur/kis/src/8c3a85a9899f117d2fa273b6c7948402d780fb46/widget.h?at=master>
Please excuse this mistake
-Philippe
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--
Philippe "xaccrocheur" Coatmeur
http://bitbucket.org/xaccrocheur / https://github.com/xaccrocheur
http://opensimo.org/play/
3468
days inactive
3469
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
3 participants
participants (3)
-
Harry van Haaren -
hermann meyer -
Philippe Coatmeur