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

Signal tracing #3

Open
covex opened this issue Oct 5, 2017 · 3 comments
Open

Signal tracing #3

covex opened this issue Oct 5, 2017 · 3 comments

Comments

@covex
Copy link

covex commented Oct 5, 2017

RFE: Any kind of signal tracing would be very helpful. It is fine it shows a signal definition in the hover but showing where else it is used in assignment or port map would be even better.

@TheClams
Copy link
Owner

TheClams commented Oct 6, 2017

Not sure how you would want this to work, it looks like just a simple search result function, but maybe I did not get your point.

@covex
Copy link
Author

covex commented Oct 6, 2017

It depends how complicated we want this - the simplest way would be to show in the hover also a references to the files:lines were the same signal/port name is (like e.g. for entities) - this probably is only a "simple search". If this should be smarter, then it should only take into account the entity and architecture, where this signal is used. Super smart would be to follow the signal thru the hierarchy (port maps, assignments) something like when the vhdl show hierarchy is displayed.

@TheClams
Copy link
Owner

TheClams commented Oct 6, 2017

OK, could be interresting indeed

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

No branches or pull requests

2 participants