Hi Chris,
Thanks for noticing the regression and posting about it here. We can
definitely be bothered, but as a group mostly moved forward by
volunteers it's really helpful to have the extra sets of eyes finding
these issues as they come up.
The fix should be on the maint-3.8 branch in the next day and will be in
the next stable release.
https://github.com/gnuradio/gnuradio/pull/3391
Cheers,
Derek
On 13/04/2020 23:57, Chris Vine wrote:
OK, understood. I'm only a peripheral user, so if the gnuradio
developers can't be bothered, then I can't be bothered.
------------------------------------
On Mon, 13 Apr 2020 17:57:30 +0200
Volker Schroer <[email protected]> wrote:
Ok, then you should fill a pr or report an issue.
Otherwise this issue won't be fixed I'm afraid.
-- Volker
Am 12.04.20 um 22:08 schrieb Chris Vine:
Yes, on testing it that does work.
But surely, as I said, this needs to go into the 3.8 branch of gnuradio
so that it is in the next 3.8 release?
Chris
--------------------------------
On Sun, 12 Apr 2020 17:16:24 +0200
Volker Schroer <[email protected]> wrote:
I think, it should be possible to take the qtgui_chooser.block.yml file
from the master branch. This sould work, as there is no code affected.
Volker
Am 12.04.20 um 14:56 schrieb Chris Vine:
Ah, OK. This did not find its way into gnuradio-3.8.1.0. Presumably it
will apply OK to that version however? (If so I suggest it is applied
to the 3.8 branch also.)
Chris
------------------------------------
On Sun, 12 Apr 2020 11:48:56 +0200
Volker Schroer <[email protected]> wrote:
Hi !
This was fixed with #2778
See also:
https://github.com/gnuradio/gnuradio/pull/2778/files/ef5ca9fe51dc45c0332e41db36f822f145f6116a
-- Volker
Am 11.04.20 um 14:45 schrieb Chris Vine:
Hi,
On porting a gnuradio-companion flow graph from gnuradio-3.7 to
gnuradio-3.8, I noticed that there no longer seems to be a way of
setting the initial (default) selection for the Qt GUI Chooser widget.
The initial selection seems now always to be the first one in the list.
The widget is therefore no longer suitable for presenting a selection
of numeric values to the user in numerical order where you don't want
the initial default to be the highest (or lowest) value.
Is there some way around this or some other widget that is now intended
to be used for this purpose?
Chris
