FreeCAD Forum

The member attribute is an AnalysisMember object, which has a geos_beamsection attribute, but not a geos_beamsection_obj attribute.
See https://github.com/FreeCAD/FreeCAD/blob ... ls.py#L157

See https://github.com/FreeCAD/FreeCAD/pull/11948

@chennes

PyArg_ParseTuple can't take a const char *,

Am I understanding your comment correctly?
This is currently used without problems.

This type of monkey patching on FreeCAD and FreeCADGui modules or objects belonging to these modules as is currently done from the Draft workbench (for example FreeCAD.DraftWorkingPlane) is not a good practice. This type of variables or methods should be added in the Draft and DraftGui modules.

You need to add a proxy object to the Python feature App::DocumentObjectGroupPython which implement the onChanged method with the desired behavior when a property change: Plus=FreeCAD.ActiveDocument.addObject("App::DocumentObjectGroupPython","PLUS") class Proxy: def doit(self): p...

You can use the Gui.CommandAction descriptor class.
Here is an example of how you can use it: https://github.com/FreeCAD/FreeCAD/pull/9171

There is no such thing as a second parameter in GetObject. GetObject only accepts a string with the name of the object or the ID number. The FullName attribute of SelectionObject is a string that represents a tuple with the code to get the object (in your case getObject("Part001")) and a l...

If I don't misunderstand, you want to create a working plane in the active view for each document that is created. What you can do is use a DocumentObserver and add a slot that will be notified by a signal according to what happens in the system. Suppose you want to add an observer that is notified ...

I don't think adding attributes dynamically to App or Gui modules as is currently done in Draft is a good idea. You never know if you are overriding other attributes or functions. What happens if this strategy is generalized across others FreeCAD modules? Instead, the Draft working plane could be a ...

In StringIDPy.xml you have the attribute Reference='true'. Are you sure you want this? Base::Handled destructor is called but the reference count is not zero.
And the getPyObject function in StringID class is overridden. At first glance I do not see that it makes a reference increase.