In Blender 2.79, mesh vertices were highlighted in the “tweak” selection mode by holding down the “shift” key and a slight cursor movement with the right mouse button pressed. This allows quickly add vertexes to the selection without aiming each vertex with sniper accuracy.
In Blender 2.8x, this method has become unavailable due to the left click selection change. For those users who remained on “the right click select”, nothing has changed, everything works as before. The “tweak” selection was broken only for those who switched to the left click selection.
To use the “tweak” selection with the left click select, you need to make the following changes into the keyboard shortcut settings:
In Blender 2.80 and 2.81, the button for blocking mesh transformations (Manipulate center points) has been moved to the N-panel, the “Tool” tab (Options – Transform – Affect only – Locations) and changed to the checkbox.
Working with mesh geometry, it may be necessary to assign each vertex some custom properties or data that must be written to the blend-file when saved, and which must be accessed later.
However, an attempt to assign the necessary data to the vertexes through the creation of custom properties fails. Instead of the custom vertex property, only a tuple with reference to the type of the property is created.
Render starts in a new window in Blender 2.81 by default. And there is no more render display mode settings in the “Render” menu. These settings were moved into the “Preferences”. To configure render execution window – open the “Preferences” window, press the “Interface” button and in the “Temporary Windows” configure the “Render In” parameter as you need.
Due to the nodes structure changes in the latest Blender 2.81 release, all open materials in the BIS library have been updated for this version of Blender. Compatibility with younger versions of Blender could be lost (depends on the nodes used in the material).
Button click in basically connected with the operator calling in Blender user interface. However, some times actions, that need to be performed when a button is pressed, are quite simple and do not require a separate operator for them. And it makes no sense to fill a registered operators stack with a multitude of specific operators designed to perform one highly specialized function. It would be much more convenient to associate a button press with a separate function call but the Blender API allows to associate buttons only with an operator call.
To solve the problem of creating a separate operator for each button we can use the fact that the operator can be called with the input parameters.