[Bf-funboard] node editor UI behavior questions
bassam at urchn.org
Sun Jul 28 18:48:05 CEST 2013
On Thu, 2013-07-04 at 21:42 -0700, David Jeske wrote:
> I'm confused by some behaviors in the Node Editor.
> I find the shifting of inputs really helpful when I'm trying to SWAP two
> However, when I'm adding a new input to replace an existing one, the
> behavior is really annoying. It erroneously shifts the other input down to
> an empty input, and sometimes I don't even notice right away. For me this
> makes replacing an input a two-step operation (remove old input add new).
I also find this one less useful - it might be a good idea to limit it
to specific situations where the inputs are equivalent? for instance,
inputs for math nodes, or color mix nodes, or shader mix nodes, where
the old and new wires are going into the same type of thing (values to
be math'ed, colors or shaders to be mix) but remove the behavior in
> I'm considering providing some visual feedback that this will happen, with
> a modifier key to prevent it during the drop. However, before I do this
> work, I want to make sure this is actually behavior someone likes. If not,
> it could just be removed when adding a new input (it would still work
> during swap). Are there common cases where "shift input on adding new
> input" is helpful?
> ---- Next...
> I **really** like the way I can drop a node directly onto a connection to
> splice it in. And I **really** wish it did the opposite when removing
> (closing the gap), at least if the deleted-node was a 1-video to 1-video
> node. Thoughts?
yeah, that exists, with a key modifier. a bit hard to remember for me!
> Bf-funboard mailing list
> Bf-funboard at blender.org
More information about the Bf-funboard