The first field to set (after the name) is the modifier's type. I will focus on some essential fields and leave the others to your exploration, because depending on what your modifier does you'll not need all of them. The meaning of the different fields is well explained in this header file, so you should definitely take a look. The struct ModifierTypeInfo is defined in source/blender/blenkernel/BKE_modifier.h (at line 139 at the time I write this, i.e.
* structSize */ sizeof(PizzaModifierData), So, create this file, and add it to the list of files to build in the CMakeLists.txt of the parent directory (together with all other lines starting with intern/MOD_).Īt the very least, your MOD_pizza.c file must contain: The modifier type info variable is typically defined in a file called MOD_pizza.c located in /./blender-git/blender/source/blender/modifiers/intern. To match the coding style and play nicely with the existing macro, this variable must be called modifierType_Pizza (where "Pizza" is your actual modifier name, capitalized). We'll then register it in the global list of modifiers. Core modifierĬreating a modifier means defining a global variable of type ModifierTypeInfo. Most of our changes will be located in the directory /./blender-git/blender/source/blender/modifiers/. The last points are achieved using the DNA/RNA mechanism present at the heart of Blender's architecture. But we must also ensure that it is listed in the UI, that it can be accessed through the Python API, and that its parameters are saved in blend files.
Blender change font thickness code#
So, what do we have to change? And why do we need to change so many files? Obviously, we must at least code the behavior of the modifier itself. I don't know what it can do, but at least we are sure not to get confused by other occurrences of the word "pizza" in the source base. Throughout this post, we will add a "Pizza" modifier.
/blender-git/blender $ git checkout -b pizza-modifier
0 kommentar(er)
