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

Source modules' code ports should be control parameters #973

Open
remram44 opened this issue Dec 9, 2014 · 2 comments
Open

Source modules' code ports should be control parameters #973

remram44 opened this issue Dec 9, 2014 · 2 comments

Comments

@remram44
Copy link
Member

remram44 commented Dec 9, 2014

Now that we have control parameters, it seems to me that some input ports should be changed. For instance, the code ports are urlencoded and meant to be edited from the configuration widget; showing them looks bad, editing them directly is useless, and getting/setting the parameter from code is awkward and already only works if it's a function and not a connection.

The main issue is that it completely hides where the data comes from, as there is no way to see control parameters in the UI (apart from the specific configuration widget).

@rexissimus
Copy link
Member

I think this is a good idea. Control parameters are already visible in the diff. We could also show them in the "Module Info" tab like we do with annotations, but there is no room for it in the current layout...

@remram44
Copy link
Member Author

Meeting discussion: let's do this, but should make sure that upgrade is super-safe.

@remram44 remram44 changed the title Should source modules' code ports be control parameters? Source modules' code ports should be control parameters Dec 10, 2014
@remram44 remram44 added this to the version 3.0 milestone Oct 5, 2016
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

2 participants