Interface, FileSystem, etc

File System

• Automatic removal of resources .

• Delete Materials that are not used .

• Fix 'Missing Files' (Pink textures) .

Interface

• Workspaces :

  • 'Outliner -> Blender File': In this tab it is possible to create, rename, and copy/paste Workspaces between different Blender files.

  • Workspaces: Save a workspace as default startup .

• Load UI :

  • *Note:

    • If the file is saved after being opened, it will overwrite the previous UI with the currently used UI. This happens regardless of whether you open with the original file UI or a default UI.

  • Disable loading UI from an existing file by default .

  • Disable UI loading when using Open .

Backup system

• Use of '.blend1' file and how to open it .

• Rename the .blend1  to .blend .

Source Code

• https://developer.blender.org/docs/handbook/building_blender/

• https://developer.blender.org/docs/handbook/new_developers/navigate_code/

Keymapping

• [3.6.1 to 4.1.0]

General rule

• Delete keymaps:

  • Never delete any keymap, unless necessary; do not delete just for 'cleaning'.

  • If you need to delete a 'keymap', avoid deleting a single keymap as much as possible, i.e., only delete keymaps when there is at least one other keymap that performs the same function.

• It is not necessary to use the 'export all keymaps' option. Exporting only the 'deltas' of the keymaps is useful when comparing changes between presets.

Silly things

• Any change to a 'keymap' in the preset creates an entire huge category in the .py file, making maintenance of what changes were made ridiculously and unnecessarily difficult.

• When making a change in a preset, there is a high chance that these changes will also alter the 'Blender' preset. This happens if the change you want to make did not initially exist in the preset, so Blender thinks the best way to handle this is to alter the 'Blender' preset to make the shortcut work.

  • Because of this, you must be very CAREFUL using RESTORE , as it may not restore multiple presets at the same time due to high keymap dependency.

  • IF YOUR PRESET HAS ANY 'RESTORE' , do the following: Export the preset -> delete the previous preset -> reimport the preset -> finally restore the 'Blender' preset.

    • If this is not done, the modifications will be linked to presets. This also indicates that there are "unsaved changes" in your preset.

Export

• Exporting causes Preferences to be "lost", as Export only saves the 'delta' of keymaps. The truth is that Preferences can be saved, as long as the keymaps altered by Preferences are saved along with the preset, by altering something small in the keymap.

Import

• When Import is done, the new preset becomes part of 'userpref' and is independent of the .py file used. That is, when altering something in a preset and clicking 'Save Preferences' in the lower-left corner, all presets are saved in the 'userpref' file.

• The preset made by Import will have 'restores' available if a keymap is changed, but this Restore only restores the Keymap to the initial version of the .py file, i.e., it does not restore the factory version.

• 'Keep Original': Chooses whether the .py file should be deleted after Import. Keep the option checked to retain the file.

Removing presets

• It is not possible to remove 'Blender', 'Blender 27x', or 'Industry Compatible'.