Description
Hi guys, first of all, thank you very much for your valuable contribution.
Feature Description:
Once again something floated in my mind and I thought I propose 2 similar ideas that I think those could be useful.
I'm not sure how feasible it is and if it'd be resource intensive.
I thought something like to fetch the path of an external/hierarchical name inside a module would be cool.
Like recursively try to find a signal's path where it's instantiated and/or auto-completion lists the objects.
For example we have this signal called test_123. This is defined in module test_3.vhd. test_3 entity is instantiated in test_2.vhd and test_2 on the other hand is instantiated in test_1.vhd. If we now instantiate the test_1.vhd in tb_test1.vhd and we want to access the test_123 signal, this would follow as for example:
alias test_123 << signal .tb_test1.DuT.test_2_inst.test_3_inst.test_123: std_ulogic >>;Idea 1
Right click on the test_123 signal and click on a trace button or something like that and copy the path.
Idea 2
If we write ...
<< tb_test1.DuT. ... >>... the auto-completion pops up and proposes all of the signals within the given instantiation label.
Feature use case:
This would heavily reduce the time to look for the signals' path names together with their types are also alongside fetched.