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

Visualizer changes protocol if mismatched protocols assigned to same port #4117

Closed
Fonzi03 opened this issue Nov 11, 2023 · 1 comment
Closed

Comments

@Fonzi03
Copy link

Fonzi03 commented Nov 11, 2023

2023.19
I believe in a previous version (I'm remembering maybe November of 2019)

When you opened visualizer and had a protocol assigned to a port, it would not allow you to drop an incompatible protocol on the same bank of ports or gave an error/warning.

The current behaviors is that it allows you to drop them on the port and changes their protocol.

This behaviour is unexpected because now your protocol you assigned to that prop is changed and you may possibly have not realized you dropped it on an bank which would have caused that.

I feel it would be best to warn/prevent the user from dropping incompatible protocols onto ports and not change the protocol of the last assigned string to match.

@cybercop23
Copy link
Collaborator

Assuming you are running on Windows... you can easily install (override or in a new place) an older version and try it. Then install and replace the latest one. If the behaviour is diff, please include screen shots or screen recording.

If no longer an issue, please close this.

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