| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
os.path.sep is unreliable in Windows ("\" in official python, "/" in MSYS2)
With this change os.pathsep is used instead to get the path separator:
":" (*nix) or ";" (Windows)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After blocks are unselected, it's necessary to trigger an Action so that
keystroke action handlers will be updated in Application._handle_action.
In my previous pull request, I achieved this by replacing a
FlowGraph.update_selected() call with a
FlowGraph.update_selected_elements() call, since the latter happens to
trigger an Action. However, this does not occur in all cases, because
FlowGraph.update_selected_elements() can return early.
To fix the issue, I've reverted that change and changed the
DrawingArea's focus-out-event handler to explicitly trigger
Actions.ELEMENT_SELECT().
After this change, blocks appear to be unselect in all cases when
accessing the block search box.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A confluence of bugs introduced while updating GRC to Python 3 results
in keystrokes being sent to the drawing area while typing in the block
search box.
First, the drawing area needs to be placed in a Viewport before being
added into a ScrolledWindow. Fixing this allows the drawing area to grab
focus as intended when it is clicked.
Second, the drawing area needs to unselect all blocks when it loses
focus so that the relevant keystroke actions can be disabled. This
functionality was commented out during the transition to Python 3, and
I've restored it here.
|
|
|
|
| |
This reverts commit 2ff628894b645d22325db6569fdccb265f57fbe1.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
GRC used `gr.io_signaturev` to generate hierarchical block signatures.
This was only a SWIG alias to `gr.io_signature.makev`. Now, the
generator calls `gr.io_signature.makev` directly.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
previously the first hit terminated further processing
|
| |
|
|
|
|
|
|
| |
Using a gtk3 dark theme makes the content of raw types in grc variable
or parameter blocks invisible. Changing the background color to a light
grey fixes this issue.
|
|
|
|
| |
...for systems with no theme set.
|
| |
|
|
|
|
| |
amongst other things, allows assert statements to use items within namespaces the blocks import
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Improving the module grc.gui.canvas.param to add length to tooltip of attributes of a block in grc.
|
|
|
|
|
|
|
|
| |
GRC reads paths from various sources, including the GRC_BLOCKS_PATH
environment variable. It can happen that paths appear twice in the list,
causing warnings about findings blocks twice.
This deduplicates the paths in the config object.
|
|
|
|
|
| |
This allows the use of other toolchains (ninja, MSVC, etc.).
Also, use all available CPU cores (equivalent of "make -j$(nproc)").
|
|
|
|
| |
This allows the use of predictable relative paths.
|
|
|
|
|
|
|
|
| |
Previously 'gtk-clear' and 'gtk-save' were shown.
Gtk.STOCK_* constants are deprecated in favor of translated strings.
But grc is English-only, so it makes sense to stick to the simple
hardcoded solution.
|
| |
|
|
|
| |
is_dark_theme() should not throw an exception gsettings is not found (can happen in Windows).
|
|
|
|
|
| |
implements support for the Meta key on macOS.
Others platforms continue to use Ctrl.
|
|
|
|
| |
shortcut help menu accordingly
|
|
|
|
| |
Fixes #3294.
|
| |
|
|
|
|
|
|
|
|
| |
This version check duplicates the work already done in the module
`GrPython.cmake` (included by the top level`CMakeLists.txt`).
It is also wrong because it uses a lexicographical string comparison.
See issue #3264.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The underlying issue is that the built in blocks all end up getting the
'cpp' flag, which is not valid for the embedded python blocks
To fix this some work needs to be done in the "Flags" class, as all the
flags added to classes that get accumulated in the build_ins list get
added to all the classes
See register_build_in
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Added support for C++ std::map<> from python dict
- Fixed default initialization of parameters in main()
- Added missing include for realtime scheduling
- Added default CMake option for std=c++11 as this is required for
gnuradio >= 3.8
- Fixed mako template to add initialization to parameter declarations in
main()
- Fixed C++ constructor initialization list generation
- Fixed parameter type determination when an lvalue is used in an rvalue
expression
- Improved determining type of C++ variables
- Added C++ support for gr_complex parameters
- Fixed C++ generation of nested container types
- Added C++ support for virtual source/sink
- Moved cmake CMAKE_CXX_STANDARD 11 option from options.yml to
CMakeLists.txt.mako
- Fixed qtqui_sink to allow multiple instances
- Revised virtual connection processing in cpp_top_block.py
Reviewed-By: Håkon Vagsether <hauk142@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
The import of eng_notation was removed in 678a7c2ad, and so float parameter
blocks were leading to flowgraph compilation error.
Since eng_notation is still imported in the generated python script, we can
put the call to num_to_str in the generated script, instead of calling it
during script generation.
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|