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.

Sign up for GitHub

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

Jump to bottom

UI becomes unusable if port cannot be found #4

Open

cxbrooks opened this issue Aug 27, 2017 · 1 comment

Member

cxbrooks commented Aug 27, 2017

Note: the issue was created automatically with bugzilla2github tool

Original bug ID: BZ#4
From: @lhstrh
Reported version: unspecified
CC: accessors-devel@terraswarm.org

Member Author

cxbrooks commented Aug 27, 2017

To reproduce:

specify an accessor with a trigger and an input handler that sends an output on some output port;
save the accessor definition and hook the accessor up to a discrete clock;
right-click on the actor and go to the "ports" dialog and rename the port that is the input handler sends data on;
run the model.

Errors are being thrown each iteration, but the model is not stopped. Error windows pile up faster than they can be clicked away.

Possible solutions:

Report the error once, then stop the model;
Report the error silently, on the console;
Check whether all required ports are present in preinitialize(), or after attempting to make any port modifications through the GUI.

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