FeaturePython methods
Introduction
This page serves as a reference for the available overridable methods on Create a FeaturePython object part I or Scripted objects.
Primary reference
The below methods account for ~99% of the use-cases power-users may have for Python proxy classes.
++++
| | Called during document recomputes | Do not call recompute() from this method (or any method called from execute()) as this causes a nested recompute. |
| execute(self, obj) | | |
| | | |
++++
| | Called before a property value is changed | |
| onBeforeChange(self, obj, prop) | | prop |
| | | |
| | | is the name of the property to be changed, not the property object itself. Property changes cannot be cancelled. Previous / next property values are not simultaneously available for comparison. |
++++
| | Called after a property is changed | |
| onChanged(self, obj, prop) | | prop |
| | | |
| | | is the name of the property to be changed, not the property object itself. |
++++
| | Called after a document is restored or a FeaturePython object is copied. | Occasionally, references to the FeaturePython object from the class, or the class from the FeaturePython object may be broken, as the class __init__() method is not called when the object is reconstructed. Adding self.Object <nowiki>=</nowiki> obj or obj.Proxy <nowiki>=</nowiki> self often solves these issues. |
| {{Incode|onDocumentRestored(self, obj)}} | | |
| | | |
++++
It is not uncommon to encounter a situation where the Python callbacks are not being triggered as they should. Beginners in this area can rest assured that the FeaturePython callback system is not fragile or broken. Invariably when callbacks fail to run it is because a reference is lost or undefined in the underlying code. If, however, callbacks appear to be breaking with no explanation, providing object/proxy references in the onDocumentRestored() callback (as noted in the first table above) may alleviate these problems. Until you are comfortable with the callback system, it may be useful to add print statements in each callback to print messages to the console during development.
Additional methods
The below methods are for advanced usage of Python proxy classes and you won\'t have a need for them most of the time.
- mustExecute
- getViewProviderName
- getSubObject
- getSubObjects
- getLinkedObject
- hasChildElement
- isElementVisible
- canLinkProperties
- allowDuplicateLabel
- redirectSubName
- canLoadPartial
- onBeforeChangeLabel
Determining available Python methods
Within the FeaturePython Template Class exists various () calls.
Each of these correspond to an available bound Python method.
For example, imp->execute() on line 193 means the execute method is available.
Note, getPyObject() and init() are special-cases and don\'t follow the above heuristic.
See also
- FreeCAD GitHub: FeaturePython.h - public API
- FreeCAD GitHub: FeaturePythonT template class
- FreeCAD Forum Discussion: Scripted Objects Complete Method Reference
⏵ documentation index > Developer Documentation > Python Code > FeaturePython methods
This page is retrieved from https://github.com/FreeCAD/FreeCAD-documentation/blob/main/wiki/FeaturePython_methods.md