Mesa Confguration Tool Update

HansU wrote:

I'm working on a bug that if a comment is on the line before a section the rest of the comments get out of place because the configparser puts a blank line before each section and that throws the position off for following comments.

And also the parser fails loading when there is no blank line before a section.

Boolean values can be any of 1, true, True, yes, Yes or 0, false, False, no, No even though the docs fail to mention that.

Maybe I should extend the docs concerning this.

The configuration tool will now load any valid boolean value for a checkbox but will write back True/False because that is the value returned from .isChecked().

Great!

MIN_VELOCITY and MIN_LINEAR_VELOCITY were introduced in EMC 2.3 and I've not heard of anyone wanting to depreciate MIN_VELOCITY. Having said that MIN_LINEAR_VELOCITY is more descriptive of what the key is.

But they mean exactly the same, right?
It sounds that MIN_VELOCITY could be valid both for MIN_ANGULAR_VELOCITY and MIN_LINEAR_VELOCITY even though this makes not much sense.

Thanks, I'll check on the parser with no blank line in between a section end and start.

AFAIK MIN_VELOCITY and MIN_LINEAR_VELOCITY are the same thing, but I've not looked at the code to find out.

The best is a short bit on valid boolean values for the ini file and have each ini item that expects a boolean to just say boolean with a link to valid booleans perhaps.

JT

HansU wrote:

I'm working on a bug that if a comment is on the line before a section the rest of the comments get out of place because the configparser puts a blank line before each section and that throws the position off for following comments.

And also the parser fails loading when there is no blank line before a section.
 

I can't reproduce that here...

JT

HansU wrote:

on build config in ini2 branch:

File buildini.py line 28, in function get_sections
Error: [Errno 2] No such file or directory: '.ini'
["FileNotFoundError: [Errno 2] No such file or directory: '.ini'\n"]
 

 

I stopped  working on ini2 when I could not get satisfactory results from the python configparser. I've written test code that updates the ini file without using configparser and does not change anything except those key value pairs used by mesact. I'm putting that code in ini3 branch. However the team at pyqt has broken python3-pyqt5 in debian 13 so I can't test the tool until they repair it and I can install it again... I did an update and didn't pay attention that it was removing python3-pyqt5!

JT

HansU wrote:

AFAIK MIN_VELOCITY and MIN_LINEAR_VELOCITY are the same thing, but I've not looked at the code to find out.


MIN_VELOCITY is only possible in axis as alternative to MIN_LINEAR_VELOCITY.

And it is valid  in the SPINDLE_<N> section.

So almost everywhere is MIN_LINEAR_VELOCITY used (29 hits compared to 9 where 4 of them are related to the SPINDLE_<N> section). so I would suggest to change that

I changed that a while back when you first mentioned it.

Hmm looks like I was on the ini2 branch when I changed it...

JT

Work on the ini3 branch is coming along very good, I have all the details worked out just need to complete all the ini sections in the updateini.py file.

JT

gnipsel.com/mesa/mesact/index.html is the old location for the Mesa Configuration Tool. I need to remove it...

JT