From 470e11a1f8a2f8f4b5cef39f7bf77d83c71966d8 Mon Sep 17 00:00:00 2001 From: Martin Braun Date: Tue, 9 Jun 2020 16:30:26 +0200 Subject: filter API: Fix Python bindings and multi_usrp calls This fixes the following issues: - The Python bindings did not declare parents for the various filter object classes properly. This meant that set_?x_filter wouldn't work, because the user would pass a specific type (e.g., analog_filter_lp), but the class would not recognize it as a filter_info_base. - In multi_usrp.cpp, filter names are also property tree paths to make them unique. However, the setters and getters for filters would then prepend the FE path again, thus breaking those calls. --- host/lib/types/filters_python.hpp | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'host/lib/types') diff --git a/host/lib/types/filters_python.hpp b/host/lib/types/filters_python.hpp index 76b2c3a49..7210faa21 100644 --- a/host/lib/types/filters_python.hpp +++ b/host/lib/types/filters_python.hpp @@ -31,13 +31,14 @@ void export_filters(py::module& m) .def("get_type", &filter_info_base::get_type) .def("__str__", &filter_info_base::to_pp_string); - py::class_(m, "analog_filter_base") + py::class_( + m, "analog_filter_base") .def(py::init()) // Methods .def("get_analog_type", &analog_filter_base::get_analog_type); - py::class_>(m, "analog_filter_lp") + py::class_>(m, "analog_filter_lp") .def( py::init()) -- cgit v1.2.3