I’m using old-school message queues to do some thing with async messages
from UHD. I have written a custom C++ block, which I was hoping would
have
a single msgq based input.
However, I’ve found that the work() function never gets called for an
incoming msg unless I add stream based I/O. Does this sound right?
-John
On 12/03/2014 12:59 AM, John M. wrote:
I’m using old-school message queues to do some thing with async messages
from UHD. I have written a custom C++ block, which I was hoping would
have a single msgq based input.
However, I’ve found that the work() function never gets called for an
incoming msg unless I add stream based I/O. Does this sound right?
Yeah, it does. Since the legacy, bit-rotten message queues are not built
into the scheduler, no one is telling the block to run work().
Ping me (on- or offline) if there’s any trouble with the gr-uhd
components or features you could use in there.
Cheers,
M
Customer. Stuck in ancient GR that doesn’t have all of your
awesome/recent features on gr-uhd.
-John