[Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [38452] trunk/blender/source/blender/ editors/space_node/node_header.c: Removed the autoconnect call when adding new nodes, this hardly ever gives usable results and leads to annoy

[Matt Ebb]

I agree the old behaviour was pretty awful sometimes. Perhaps it can be
improved by making it more explicit and context sensitive.

For example in Houdini if you add a node (RMB/Tab) on empty space in the
network view, it will add the node on its own, where if you RMB to add a
node, but clicking on an existing node's output, it will connect the new
node up to that output. This is really handy, and *much* better than
preferences or alternate hotkeys for different versions of the same too (I'm
not too keen on how this is creeping into blender's compositor).

Same in Fusion (compositor) - adding a node clicking in empty space will add
it on its own, clicking on an existing node will insert it after that node
in the stream.

Matt


On Mon, Jul 18, 2011 at 3:37 AM, Daniel Salazar - 3Developer.com <
zanqdo at gmail.com> wrote:

> This should not come back as it was. Some specific cases like the mix
> node can be an exception but the rest is just total madness
>
> Daniel Salazar
> 3Developer.com
>
>
>
> On Sun, Jul 17, 2011 at 11:33 AM, PabloVazquez.org <venomgfx at gmail.com>
> wrote:
> > Its been a topic for a while already, but in my perspective, -1 on this.
> >
> > In 2.4x was more intuitive, adding a Mix node with two nodes selected
> > (say two rgbcurves) will automatically connect them, saving time, of
> > course would be better if they connect in the order we select them, so
> > is more predictable but still was better than now only connecting with
> > the active node.
> > Another example, adding a Separate RGB then Combine RGB node would
> > connect all of the inputs/outputs in 2.4x, not the case in 2.5x.
> >
> > I know is easier to remove than to fix, but at least should be a
> preference.
>