The error I'm seeing has something to do with gui hints. If no gui hint is
give, there is no error.

On Mon, May 3, 2021 at 4:42 PM Jeff Long <willco...@gmail.com> wrote:

> Using GNU Radio 3.8.3.0 on Linux, I do not see anything about disconnected
> ports. But, there is a rather ugly error message that comes up about
> comparing NoneType vs int. No ideas at the moment.
>
> You may also add an issue to https://github.com/gnuradio/gnuradio/issues,
> where it will be tracked.
>
> On Mon, May 3, 2021 at 3:10 PM Ralf Gorholt <ralf.gorh...@gmx.de> wrote:
>
>> Dear all,
>>
>> I have spent several hours before my PC trying to get my new OOT block
>> running, but in vain. Now I have got the impression that one of my
>> problems is due to a bug in GNU Radio (Companion). I have attached a
>> working graph (using Qt GUI) to this email. I am not used to report bugs
>> but in the wiki I have read that I should send an email to this list.
>>
>> The problem is, that in certain cases when I change the value of a
>> parameter in a combo box, GRC displays a message telling me that ports
>> are disconnected although they are not.
>>
>> This behaviour can easily reproduced. In GRC, load the attached flow
>> graph and open the properties window of a block that has a combo box.
>> Then, change a parameter and click the "Apply" button. The value in the
>> block changes. Then change the value back. As soon as you select the
>> item in the combo box, a message is displayed telling you that the ports
>> are not connected and no more changes are accepted, even when you click
>> on "Apply".
>>
>> I have verified this with GNU Radio version 3.8.2.0 on Linux (Python
>> 3.8.5) and 3.8.0.0 on Windows (Python 2.7.10). GNU Radio 3.9 (checked on
>> Windows) does not show this behaviour but if I remember correctly, not
>> everything has been ported to version 3.9 yet and for this reason I
>> would like to keep version 3.8. Would it be possible to fix this bug
>> also in version 3.8?
>>
>> Thank you very much for your help.
>>
>> Kind regards,
>>
>> Ralf
>>
>

Reply via email to