index_lathe_tool_with_wear and G43

I have a setup in which I'm trying the index_lathe_tool_with_wear remap straight from stdglue.py.  After an execution of 'Tn',  the correct tool offset is explicitly set in index_lathe_tool_with_wear() with a couple invocations of 'G43 Hn'.  However, a subsequent execution of 'G43' without specifying an H number loads the tool offsets from the previously loaded tool instead of the new (current) tool - I noticed that Interp::convert_tool_length_offset() assumes that the offsets for the current tool have been copied into the 0th entry of settings->tool_table, but it seems that it does not happen (until the next toolchange), so it retains the values from whatever tool was previously there.  Is this a correct behavior? and if not, what would be a clean way to fix it?

You probably have found a bug, but why are you issuing a g43 after the tool change?

Chris

Prior to enabling the index_lathe_tool_with_wear, I had used the default M6 map, so I did tool changes with Tn; M6; G43; I would assume that after the remap, the same G-Code sequence should produce a similar result: the M6 would be ignored and the G43 would load the offsets for the current tool (perhaps without adding the wear offset). Since G43 now loads an incorrect offset, I will not be issuing it after the tool change.

For general safety, it would be nice if G43 never put the tool offsets in an inconsistent state - The dirtiest workaround I can think of would be to remap G43 so that it fails with an error unless the H number is specified, but I was hoping maybe there's a cleaner way. If it is a bug, should I post this issue on github?

IIRC m6 will mess things up too. There is a remap to ignore m6 that I recommend.
I am not sure if g43/43.2 can be made to be ignored - would have to look into it.

I believe in most commercial controls m6 and g43 are not used at all for lathes.

Posting on githubs can helps to have it worked on.

No, I do not have RANDOM_TOOLCHANGER set in the INI.