kindred/create
1
1
Fork 0
Code Issues 53 Pull Requests Actions Packages Projects 9 Releases 2 Wiki Activity

FEM: Fix typos in python post processing code

Browse Source
This commit is contained in:
Stefan Tröger
2025-05-02 09:25:48 +02:00
parent 346558ab71
commit f3edddcbdb
3 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
cMake/FreeCAD_Helpers/SetupSalomeSMESH.cmake
View File

@@ -65,7 +65,7 @@ macro(SetupSalomeSMESH)
set(BUILD_FEM_VTK ON)
# Check if PythonWrapperCore was found
# Note: vtk 9 only, as the implementations use the vtk modules introduced in 9.0
# Note: VTK 9 only, as the implementations use the VTK modules introduced in 8.1
# VTK_WrappingPythonCore_FOUND is named differently for versions <9.0
if (${VTK_WrappingPythonCore_FOUND})
set(BUILD_FEM_VTK_PYTHON 1)

6
src/Mod/Fem/App/AppFemPy.cpp
View File

@@ -82,11 +82,11 @@ public:
"detected from file suffix)");
add_varargs_method("getVtkVersion",
&Module::getVtkVersion,
"Returns the VTK version freeCAD is linked against");
"Returns the VTK version FreeCAD is linked against");
#ifdef FC_USE_VTK_PYTHON
add_varargs_method("isVtkCompatible",
&Module::isVtkCompatible,
"Checks if the passed vtkObject is compatible with the c++ VTK version freecad uses");
"Checks if the passed vtkObject is compatible with the c++ VTK version FreeCAD uses");
#endif
#endif
add_varargs_method("show",
@@ -349,7 +349,7 @@ private:
throw Py::Exception();
}
// if non is returned the vtk object was created by annother vtk library, and the
// if non is returned the VTK object was created by annother VTK library, and the
// python api used to create it cannot be used with FreeCAD
vtkObjectBase *obj = vtkPythonUtil::GetPointerFromObject(pcObj, "vtkObject");
if (!obj) {

6
src/Mod/Fem/App/FemPostFilterPy.xml
View File

@@ -31,7 +31,7 @@
<Methode Name="getInputData">
<Documentation>
<UserDocu>
Returns the dataset available at the filters input.
Returns the dataset available at the filter's input.
Note: Can lead to a full recompute of the whole pipeline, hence best to call this only in "execute", where the user expects long calculation cycles.
</UserDocu>
</Documentation>
@@ -39,7 +39,7 @@ Note: Can lead to a full recompute of the whole pipeline, hence best to call thi
<Methode Name="getInputVectorFields">
<Documentation>
<UserDocu>
Returns the names of all vector fields available on this filters input.
Returns the names of all vector fields available on this filter's input.
Note: Can lead to a full recompute of the whole pipeline, hence best to call this only in "execute", where the user expects long calculation cycles.
</UserDocu>
</Documentation>
@@ -47,7 +47,7 @@ Note: Can lead to a full recompute of the whole pipeline, hence best to call thi
<Methode Name="getInputScalarFields">
<Documentation>
<UserDocu>
Returns the names of all scalar fields available on this filters input.
Returns the names of all scalar fields available on this filter's input.
Note: Can lead to a full recompute of the whole pipeline, hence best to call this only in "execute", where the user expects long calculation cycles.
</UserDocu>
</Documentation>