On 30 October 2016 at 14:47, Jim Craig <jimcraig5...@windstream.net> wrote: > Since the current functionality reads a running configuration, I would > like to be able to read the .ini file that is currently loaded to get > access to the .hal files that make up the current running configuration.
I would actually suggest that the tool should start by asking for a single HAL file, or the INI file for the config to be examined. In the case of an INI file being the top-level, each HAL file from the INI could be represented by a meta-block, joined by the shared HAL signals. Double-clicking the block would take you into that specific HAL file. I have done a fair bit of graphical programming in LabView, and my current job working on engine control software requires me to pore over a total of 28,000 PDF pages of block diagrams that describe the software function (much of the software is defined in Simulink then auto-coded) so I have a pretty good handle on how this is normally done. I do find myself wondering if Xcos would be a good basis for a HAL editor. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1916 ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
