To clear compositing window (completely remove all nodes from it), run the following code:
|
1 2 3 4 |
import bpy nodesField = bpy.context.scene.node_tree for currentNode in nodesField.nodes: nodesField.nodes.remove(currentNode) |
In the development of add-ons, their modules should be abstracted as much as possible. For a very simple reason – functional, created for a current add-on, will likely need in the next add-on, and possibly not even in one. In the add-on release, the problem of accessing to such common functionality modules is easily solved – all the necessary modules are included in a single package and distributed together. However, during the add-ons development, such modules are much easier to store separately, in one instance, without associating them with any particular package, and import if necessary the desired modules to the desired add-on.
In accordance with the packages import rules, Python allows to refer modules in the following ways:
Blender add-ons development code reuse with symbolic linksRead More »
In the development of complex add-ons with large code volume storing all the code in a single file is inappropriate. When a single file contains logically unrelated classes, functions, and datasets, it is difficult to read, debug, find the necessary code pieces, reuse code. Such code layout is considered as very bad programming tone.
Blender Python supports modular system that allows subdividing logical code parts of the add-on into different files, and then connect them to use. Even if you have never thought about modules, creating scripts or add-ons, you have already used them – any code stored in the *.py file is a separate independent module. Just your addon consists of only one module. Complex add-ons may consist of several tens of modules.
Sometimes when debugging scripts or add-ons, errors not only interrupt the code execution but also causes the complete closure of Blender together with its system console. This case its impossible to check errors and view errors messages.
To find a failure, Blender can be started from the command line interpreter cmd. In this case, Blender output log is redirected to the cmd window which, when the program falls due to errors, not closed. If Blender closes all error messages stay available to check in the cmd window.
To start Blender from a command line interpreter:
Part of the way contains spaces must be enclosed in double quotes – like “Programm Files” in this example.
Add-on Accurate Render Border v. 0.0.2 update.
Checkbox “Width/Height” added. It allows to switch input mode between “left-top border corner coordinates – right-bottom border corner coordinates” and “left-top border corner coordinates – border width and height”.
Blender add-on allows setting accurate coordinates for render border.
After add-on installation in T-bar additional “ARB” tab appears. On this tab, it’s possible to set accurate values for left-top and right-bottom render border corners coordinates in pixels. Coordinates establish relative to the render size (Properties — Render — Dimensions — Resolution). After pressing the “Set Accurate Render Border” button render border determines in accordance with the entered values.
Add-on is free and open-source. If you want to support it – you can buy the add-on for a convenient price, or set the price to 0 to download it for free.
Blender has the ability to limit the scope of rendering – outlining a region the special render border and checking the Border checkbox on the Render – Dimensions tab in Properties window. If such frame is set – Blender render only a limited area of the image.
There are two ways to set render border via the Blender API:
All user-defined classes (panels, operators), registered in Blender API, exists only during Blender runs. After program close they are deleted from memory. Therefore, if some variables are defined in user classes, all of them will be reset after Blender restart.
However, sometimes it is necessary to use in Blender add-on variables with values that not be lost in the process of program restarting. To retain variables values, it needs to wrap them into special class – property, and attach to any object whose properties are stored in * .blend file.
Creating Blender Add-ons variables with values saved in blend-filesRead More »
User defined operator classes, inherited from bpy.types.Operator, are static. Accordingly, only static variables can be defined in them.
Static variable sampleVar definition in SampleClass class:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
class SampleClass(bpy.types.Operator): bl_idname = "sample.sample_class" sampleVar = 5 def execute(self, context): print(self.sampleVar) self.__class__.sampleVar += 1 print(self.sampleVar) print(self.__class__.sampleVar) def sampleFunc(): SampleClass.sampleVar += 1 print(SampleClass.sampleVar) |
One of the essential conditions of comfortable work is the convenience and speed of accessing add-ons functional. It is not enough to write an add-on and register it in Blender API system. Be sure to give the easy call add-on functions ability to the user. So, any add-on should determine a place to put interface buttons that provide access to its functionality.
All available Blender user interface located on panels. Three panels are the most used: T-bar – opens/hides by pressing the t keyboard button, N-bar – opens/hides by pressing the n button, and the Properties panel – called in the main menu of any window, typed it as Properties.
Blender API allows defining users panels to place add-on functional buttons on any of these three main panels.
Creating panels for placing Blender add-ons user interface (UI)Read More »
Get on Gumroad