Age | Commit message (Collapse) | Author |
|
Also:
* update texture node list (and make names consistent with blender (ending int 'Texture'))
* rename variable 'type' (which is a python keyword)
|
|
Thanks to @Severin for help on IRC :)
|
|
|
|
Forgot to check for active node and tree type.
|
|
|
|
|
|
|
|
Fixes a bug with frames, selects only the source node afterwards, reports info.
From D2129 by @poor
|
|
|
|
outputs the same if it's already connected
|
|
misleading the user
|
|
Also added option to not add the texture coord and mapping nodes, in case the user just wants the image node.
|
|
When using basically any NW function inside a 2nd (or higher) level nested node group, it would fetch instead the 1st level nodes.
Logic is now simplified and improved to find the active tree no matter how far down the rabbit hole you go.
|
|
|
|
(optionally)
|
|
far left)
|
|
|
|
|
|
another input of the output node
|
|
|
|
rB83824947 caused the old hacky method to break
|
|
|
|
Other selected nodes are arranged around the active one - I've been using this for a while and found this behavior is much more useful.
|
|
Also reduce default margin slightly, especially for spacing between vertically-aligned nodes.
|
|
Adding an image sequence now works for Shader nodes too (not sure when this broke?)
Also improved/fixed the logic of figuring out what image sequence the user is trying to add - sometimes they select only one frame, sometimes they select all the frames (Blender itself is inconsistent about this behavior)
|
|
|
|
- Increase line thickness slightly
- Draw in gray when source and target nodes are the same one (nothing will be done)
- Use DPI factor for line thickness
- Draw circles with 12 sides (32 was overkill for such tiny circles)
- Rename node outline draw callback accordingly
|
|
There's no real performance hit, so no reason not to use it all the time.
Also enable antialiasing for other draw functions.
|
|
The previous behaviour was flawed:
1. Repeatedly aligning the same selection of nodes would space them further and further apart each time
2. The user had to choose between "Horizontal" and "Vertical", which gave the opposite of intended behavior
The new behavior:
1. Nodes are spaced evenly and consistently apart
2. Whether the nodes are aligned vertically or horizontally is now determined automatically
|
|
- Only act when clicking on the background
- remove unused variables
|
|
|
|
|
|
Now correctly uses lamp output.
|
|
- Fix: Errors shown when using emission viewer without material output present
- When creating material output for emission viewer, position it in the middle of nodes (issue was that it first created the new node at `0, 0` and then calculated average Y loc)
- Remove unused var
|
|
|
|
|