I think both are valuable, (but both certainly not prio1). Can i ask you to try out http://thebrain.com make a small mindmap and navigate thru that map? Use the keyboard. Now if we can have that behaviour, with or without GUI imo that would bring focus to the component when making a configuration.
It's about navigating that mind map, and keeping focus on the thing you're doing. Install the trial, play around and visualize a component instead of a node when you navigate that map. Go on, that's an order. Report back when you have given it thought. :) can't explain more if you haven't tried it
Sorry - I do not share the enthusiasm expressed here, so I will not engage. On the order of import/urgent/wise use of scarce developer time I doubt it is either, besides being an evidently ill-defined problem (maintenance? design? inspection?).
That's what I originally said: no prio uno. Just an idea. But if the goal is re-usability also in other projects than making/changing Hal configurations is IMO important. And the current HAL file is bad in usability and readability.
:point_up: November 30, 2015 12:08 AM what would you like yourself when you're making HAL files? like the inspector idea ? would you want big overview of everything? or maybe show component xxx where you can easily fly to the component that is attached via a signal? maybe some shortcuts?