Mesa Configuration Tool

The custom.hal file is not changed by the tool when saving, it only creates it if requested and not in the configuration directory.

I'll have to ponder how to only change the values used by the tool... I do think it is possible and would be another huge benefit for using the Mesa Configuration Tool.

JT

PCW explained that to me but I forget the exact reason... I think it has something to do with pulse timing but may be wrong. And it does work without it but not as good.

JT

HansU wrote:

Furthermore it would be good if unknown key value pairs (like "BACKLASH = 0.01") are not removed when generating the config. Maybe you can add a special section for that? Or remember the lines which didn't correspond to a supported value and print them when generating? This would also allow to keep comments.

 

Based on your suggestion I've created an ini branch where I'm completely changing how I deal with the ini file.

I removed all the items that the tool uses and placed them in a hidden file .mesact.conf. This is about 1/2 done now. This will unclutter the configname.ini file.

Next I'll read in the configname.ini file and use the configparser to only update the values from my tool instead of just writing a new file like currently I'm doing now.

The configname.hal, io.hal and ss.hal files will still be created each time and as before the custom.hal, shutdown.hal and postgui.hal files will not be touched once they are created.

This is a huge change in how I deal with the files so I thought it best to create a branch to work out the details and not break the master branch while working on the change.

JT

Geez right in the middle of replying and the power went out... had to fire up the generator.

The .mesact.conf file is created when you build the configuration and is used to setup the tool when you load the ini. Not sure exactly how I will merge old and new configurations yet but that must be addressed.

I have tested my code and it doesn't change anything in the existing ini file that is added by a user so that is good.

JT

I have run into an issue with the python3 configparser, it does not allow duplicate keys and the [HAL] section can have duplicate keys for HALFILE. So I'll have to figure out how to get around that...

JT

HansU wrote:

JT wrote:

The .mesact.conf file is created when you build the configuration and is used to setup the tool when you load the ini. Not sure exactly how I will merge old and new configurations yet but that must be addressed.

 
Hmm but I saw it as a big advantage that your tool can open a config without need for additional files.
 

That is an advantage that you can share one file to create the whole configuration... I have solved the puzzle for the [HAL] duplicate keys issue. The disadvantage is the ini file gets very long... gotta ponder which way to go now.

JT