Where is the code from runString to recompute? That is python interpreter code - in itself not important. The important part is what is being executed in "runString", i.e. the interpreted python code itself. What is it doing, does it need to have the result of the recompute immediately? H...

The issue is Windows Accesibility hitting all cells in the table, even if they are empty. The correct solution would be to implement an accessibility interface for the SpreadsheetGui::SheetTableView . The other way (blech) is to disable accessibility features on the spreadsheet if you are blocked by...

Any code that executes into python, or is executed from python is subject to a global lock, to prevent concurrent modifications of python structures. It is a big issue with multiprocessing on python. See https://wiki.python.org/moin/GlobalInterpreterLock As soon as you start a new thread, it will tr...

Hey, it's python :) The global interpreter lock will throw a spanner in everything that is trying to call into it. You can try and use a fiber to serialize all calls to python to allow C++ code parallelization . There _may_ be some wins, if the C++ code is where the perf issue lies. The idea would b...

Ok, so the actual property isn't exactly 21mm. Python console expands it to: >>> App.ActiveDocument.Sketch081.Placement.Base.y 20.999999999999986 And the result for the Axle MountThickness is >>> ActiveSketch.Constraints[19].Name 'AxleMountThickness' >>> ActiveSketch.Constraints[19].Value 5.99999999...

You need to ignore the completion suggestion, and it will work.

The pending pr https://github.com/FreeCAD/FreeCAD/pull/3062 has a fix for this, the main thing - adding a LOCAL access syntax, with a leading '.'
to unambiguously specify a property.

Trying with a smaller value yields the start of some artefacts, definitely a precision issue; probably stemming from how the property is being updated after the fix.
.0000001 : With -0.001 (14.999):

It looks like the change has some side effects in my assembly... EDIT: The side effect looks to be because of improved precision. Due to the way double precision works, I need to offset .001 mm. Also, we don't have a pure 6mm in the constraint below, but 5.999999999999993 for AxleMountThickness Issu...

Hi! EDIT: found the other existing issue!: https://github.com/FreeCAD/FreeCAD/issues/7489 POSSIBLY related - https://github.com/FreeCAD/FreeCAD/issues/7589, https://github.com/FreeCAD/FreeCAD/issues/7390 I had an issue where a constraint's value would not update after setting it to an expression. Af...

This was just merged in. There is still an issue with contextual completions: If you're in a sketch and try to complete "Constraints.", but there is already a Document or an Object called "Constraints", the completer will think you're referring to that one. Adding the full sketch...