The slider adds a new requirement of PyQwt (python Qwt bindings). Qwt
should already be installed for the qtgui sinks themselves.
The qtgui and wxgui widgets are distinctly separated. Previously, the
“variable slider” was a wx slider form. Now, there is a WX GUI Slider
and a QT GUI Slider. And the generate options now have a QT GUI option.
You cannot mix and match widgets from different graphics libraries.
No attempt was made to make the existence of different graphics
toolkits transparent to the user. That would have been a huge pain on my
part and I couldn’t try new things. If this Qt thing catches on, I am
considering a migration script from wx->qt.
The Qt widgets in grc do not have a python wrapper/forms library like
they do in gnuradio. All the generated code uses the PyQt API directly.
This is in-part possible because Qwt supplies its own set of useful
wrappers around Qt widgets. Examples: http://qwt.sourceforge.net/sliders.png
Each widget block in grc has a gui hint parameter. This parameter is
a combination of the grid parameter and notebook parameter seen in the
wx widget blocks. It also allowed the implementation code to be a lot
more generic.
Whats missing?
I feel that the widgets still need a bit of polishing. Engineering
notation would be nice. I’d like to see features in the wx scope sink
brought to the qtgui scope such as trigger modes and multiple channels.
I think the qt equivalent of the numbersink would be nice too (and that
could use some of those real fancy qwt widets):
Why qtgui stuff?
The WX stuff in gnuradio is fairly polished in comparison; and when it
works, it works. But we have seen many issues with wx outside of the
linux+x86 world, not to mention opengl issues on the x86. I hope that
the qt stuff is a viable, cross platform option for live gnuradio
plotting and graphical applications.
I had a few moments to try it out. It worked very well and I think it
will be useful.
I got a little confused when I cloned the repository because it said
there was no HEAD (or something like that) and the directory was
empty, but I could still checkout to the wip/qtgui/grc branch. I hope
I got the right thing.
You mention engineering notation for the widget. I believe for the
text entry it is quite straightforward (xml attached - I just copied
the code from the gr-qtgui example).
I had a few moments to try it out. It worked very well and I think it
will be useful.
I got a little confused when I cloned the repository because it said
there was no HEAD (or something like that) and the directory was
empty, but I could still checkout to the wip/qtgui/grc branch. I hope
I got the right thing.
Ah, I dont have a master branch. Most people just git remote add my repo
to an existing gnuradio repo.
You mention engineering notation for the widget. I believe for the
text entry it is quite straightforward (xml attached - I just copied
the code from the gr-qtgui example).
Excellent, I will try to get this in the block as an option for
float/real numbers.
My goal is to have engineering notation for the text box in the qwt
slider. I think that involves making a custom qwt text/engine object. It
seems like something qwt should support or would not be hard to
implement. Not sure. http://pyqwt.sourceforge.net/doc5/reference.html
I finally got some time to take a look, but it looks like your WIP
branch has disappeared ? Did the code go into the main git repo ? I
see most of the qtgui grc blocks when starting the gunradio companion,
[from the latest repo, 19-MAR-2011] but it looks like the plotter is
missing ? Which is of course, the one I was really interestedx in
testing…
see most of the qtgui grc blocks when starting the gunradio companion,
[from the latest repo, 19-MAR-2011] but it looks like the plotter is
missing ? Which is of course, the one I was really interestedx in
testing…
Its all on the master branch of gnuradio.git
-josh
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
