I am starting to play around with 3.6.3rc0 a little bit. I’m excited
about the new message passing infrastructure and the Python-based
signal processing blocks. In fact, I would really like to be able to
create Python-based blocks that use the new message infrastructure.
However, as best I can tell this is not currently possible since the
message_port_xxx functions are not being exposed to Python. Is that
accurate? If so, are there any plans to marry them together in the
future?
Thanks,
Roy
On Fri, Jan 4, 2013 at 6:52 PM, Roy T. [email protected] wrote:
Roy
That shouldn’t be impossible to support. In general, I’m not a huge fan
of
using the Python blocks for efficiency reasons. I always look at them as
a
way to prototype an new block or algorithm before converting it into
C++.
But I know some people like to use them as framers or frame/packet
oriented
workers.
I’ve added this as Issue #508.
Thanks,
Tom
Thanks, I was able to make the modifications to get it working without
too much trouble. The only thing that was a little tricky was
registering the messaging handling callback function. I am doing most
signal processing with C++ blocks but using Python for custom GUI and
higher layer protocols so it is useful that they can communicate with
the rest of the blocks via the messaging infrastructure.
Thanks,
Roy
On Sun, Jan 13, 2013 at 6:28 PM, Roy T. [email protected]
wrote:
Thanks, I was able to make the modifications to get it working without
too much trouble. The only thing that was a little tricky was
registering the messaging handling callback function. I am doing most
signal processing with C++ blocks but using Python for custom GUI and
higher layer protocols so it is useful that they can communicate with
the rest of the blocks via the messaging infrastructure.
Thanks,
Roy
Hey Roy, that’s great!
Any chance you could respond to the Issue I created on the wiki page
with a
patch so we could put this into the main code?
Thanks!
Tom