Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Embedded Python blocks can not use gr.io_signature() #4184

Open
willcode opened this issue Feb 4, 2021 · 2 comments
Open

Embedded Python blocks can not use gr.io_signature() #4184

willcode opened this issue Feb 4, 2021 · 2 comments

Comments

@willcode
Copy link
Member

willcode commented Feb 4, 2021

GRC assumes that embedded Python blocks use the list-style input/output signature. The user sees:

Can't create an instance of your block: object of type 'io_signature_sptr' has no len()

when attempting to use gr.io_signature() for in_sig or out_sig.

@willcode
Copy link
Member Author

willcode commented Feb 4, 2021

Since there is no yml file associated with an embedded Python block, fixing this would require GRC to parse the the io_signature AND provide num_inputs/num_outputs where needed in the params dialog.

Along the same lines, it would be nice if data type could be changed from the dialog. Unfortunately, there is nowhere to specify what data types the block can accept, so no clue how this would be done.

@marcusmueller
Copy link
Member

Removing the bug tag here. It's OK that embedded blocks aren't fully-featured. The list-style iosig def is definitely a good start, and the rest can be added through enhancements

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants