Created by: portnov
Addressed problem description
We used to have "custom defaults" mechanism for nodes. Now it is removed, but even when it worked it had a problem of being too hard to use.
Solution description
Now that we have Presets and per-node presets, let's use this mechanism to replace old custom defaults mechanism. How it works:
- You configure the node as you wish
- You go to it's Presets menu (in the N panel, or in the node's context menu, or you can press Shift-P), and select "Save current settings as node preset"
- Enter Default (case sensitive) as the name of the preset.
Now, when you create node of the same type by any usual way (from Shift-A menu, from T panel, from Search menu), this Default preset will be automatically applied. This preset will not be applied when the node is created as part of another (multi-node) preset being imported.
These Default presets are available in the Presets panel under T panel; you can rename them, or remove as well as others.
Preflight checklist
Put an x letter in each brackets when you're done this item:
-
Code changes complete. -
Code documentation complete. -
Documentation for users complete (or not required, if user never sees these changes). -
Manual testing done. -
Unit-tests implemented. -
Ready for merge.