| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Josh Morman <jmorman@gnuradio.org>
|
| |
|
|
| |
Signed-off-by: Josh Morman <jmorman@gnuradio.org>
|
| |
|
|
| |
Signed-off-by: Håkon Vågsether <hauk142@gmail.com>
|
| |
|
|
|
|
|
|
| |
Issue 5032 results from an unfilled parameter erroneously indicated as
filled with a default value of 0. This PR makes grc indicate an error
when there is an unfilled parameter by returning None.
Signed-off-by: Solomon Tan <solomonbstoner@yahoo.com.au>
|
| |
|
|
| |
Signed-off-by: Jeff Long <willcode4@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
At the moment some qtgui windows do support only very simple gui hints, as
the parse_gui_hint in param.py generates independently of the output language
only python code.
This is fixed here, so the gui_hint() can be used in cpp code generation.
To test more complex gui hints the qtgui_tab_widget was extended to cpp.
After that compiling the generated cpp code for some examples led to
/usr/include/python3.9/object.h:206:23: Fehler: expected unqualified-id before »;« token
206 | PyType_Slot *slots; /* terminated by slot==0. */
This is a known error and can be fixed by
ifdef ENABLE_PYTHON
pragma push_macro("slots")
undef slots
include "Python.h"
pragma pop_macro("slots")
endif
instead of simply
ifdef ENABLE_PYTHON
include "Python.h"
endif
which was applied to the corresponding gr-qtgui header files.
Signed-off-by: Volker Schroer <3470424+dl1ksv@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I refer to the mailing list thread on May 8 2021 regarding "Embedded
Python Block Tutorial Param ID Error".
The bug is caused by #4522 as names of embedded python blocks
such as `epy_block_0` are blacklisted because of "blocks" in the
argument `black_listed_ids`. It affects both embedded python blocks and
modules. This commit fixes the bug by granting exemption for these two
types of blocks from id validation.
This commit makes the regex more strictly follow the naming convention
of epy blocks and modules so that only these will be fast-tracked
through the id validation. The naming convention appears to be a "epy"
prefix, followed by "block" or "module", and a number suffix.
This regex also takes into account the user copying-and-pasting the epy
blocks resulting in id names like `epy_block_0_0` and `epy_block_0_0_0`.
Instead of checking for epy blocks or modules using the naming
convention in the id like commit ac383d1 does, this commit checks by
looking at the block's key. All epy blocks and modules are identified
with the key `epy_block` and `epy_module` respectively.
This commit fixes the bug by changing the import name such that it does
not coincide with the generated id for epy blocks and modules. This
means that there no longer needs to be an exception case in the
validation id function for epy blocks and modules.
This commit fixes the bug by giving epy blocks and modules a new
attribute that grants them exemption from blacklist id validation.
Unlike v1, v2 and v3, this does not depend on the naming convention of
the block ids or block keys, which could change in the future, making
the code less of a hassle to maintain.
Improved on v5 (commit b85da80) with the following changes.
1. Changed `exempt_from_id_validation` from an instance variable to a
class variable since all instances of epy blocks and modules are
affected by the bug mentioned in v5.
2. Changed `hasattr` to `getattr` to prevent the bug where a block is
exempted from id validation when `exempt_from_id_validation=False`.
Improved from v6 (commit e66ed85). This grants the exemption to
blocks/modules only after they are marked for blacklist. This change
makes sure that the id exemption is used only to prevent the
blacklisting bug. The blocks/modules will still go through other forms
of id validation such as the naming convention check.
Signed-off-by: Solomon Tan <solomonbstoner@yahoo.com.au>
|
| |
|
|
| |
Signed-off-by: Volker Schroer <3470424+dl1ksv@users.noreply.github.com>
|
| |
|
|
| |
Signed-off-by: Christophe Seguinot <christophe.seguinot@univ-lille.fr>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All of the removed `from __future__ import` were needed in older
versions of Python (mostly 2.5.x and below) but later became mandatory
in most versions of Python 3 hence are not necessary anymore.
More specifically, according to __future__.py[1]:
- unicode_literals is part of Python since versions 2.6.0 and 3.0.0;
- print_function is part of Python since versions 2.6.0 and 3.0.0;
- absolute_import is part of Python since versions 2.5.0 and 3.0.0;
- division is part of Python since versions 2.2.0 and 3.0.0;
Get rid of those unnecessary imports to slightly clean up the codebase.
[1] https://github.com/python/cpython/blob/master/Lib/__future__.py
|
| |
|
|
|
|
|
|
| |
This commit adds a new parameter type to GNURadio Companion that allows
you to select directories using a gui. This functionality is
very similar to that of the previously available "file_open" and
"file_save" parameter types, and mainly differs by calling GTKs file
chooser with FileChooserAction.SELECT_FOLDER.
|
| |
|
|
|
|
|
|
|
|
|
| |
This feature adds the ability to insert arbitrary code into the python
flowgraph. It gives a little more low-level flexibility for quickly
modifying flowgraphs and adding custom bits of code rather than having
to go and edit the generated py file
One example is synchronizing multiple USRP objects - sometimes you want
different sync than what is offered in the multi-usrp object, so you can
put a bit of code in the snippet block to do the custom synchronization
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The block_id parameter for the block being probed was being validated as
a block_id. But there is a use case where this can be blank to call a
function on the flowgraph object itself.
Changed the block_id dtype to "name" just like function_name. Could
have just changed it to raw and done no validation, but that doesn't get
displayed very nicely in the grc block
Fixes #2966
|
| |
|
|
|
|
|
| |
committing the fix suggested by @haakov
Make gui_hint collisions show up as validation errors
Fixes #2287
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Due to the way stringify_flag is called, the block_id,
function_name and function_args are all given extra
quotes which cause issues when generating the python source
change/add new dtypes for function_probe
Fixes #1783
|
| |
|
|
|
| |
Previously only python scientific notation was supported.
Now engineering notation e.g. k,M,G is supported as input format as well.
|
| | |
|
| |
|
|
|
|
| |
Enabling the option_attributes to be accessed by the rest of the
block's parameters by using a new string subtype. Also adding
validation.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
grc 3.8 should treat
window@index or
window@index :i,j,k,l
differently to what grc 3.7 does.
|
| | |
|
| | |
|
| |
|
