<div dir="ltr"><div>@Francesco, I've posed a question on bf-funboard with some scenario descriptions<br></div><div><div><br></div><div>@Tobias, the notion of input and output node preservation answers the question I posted bf-funboard. (I'm sure this won't be the first time this will happen.) Apparently, when you have a single node *all* input and output is "preserved", if you insert two nodes that are connected together (no input or output connections), there is nothing to preserve so the new group input/output nodes are detached.</div></div><div><br></div><div>Thanks for the input. I should [solve] this on bf-funboard.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 2, 2017 at 8:36 PM, Aaron Carlisle <span dir="ltr"><<a href="mailto:carlisle.b3d@gmail.com" target="_blank">carlisle.b3d@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey sorry I was unable to get to your stuff over the weekend I was busier than I thought I would be.<div>I will have a look soon though!</div></div><div class="gmail_extra"><br clear="all"><div><div class="m_2823388549611861073gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><span style="color:rgb(153,153,153)"><span style="color:rgb(0,0,0)">Aaron Carlisle</span><br></span><div><span style="color:rgb(153,153,153)"><br>Picture taker | Bit cruncher | Pixel pusher | Document writer | Artist<br></span></div><div><span style="color:rgb(153,153,153)">Project administrator for the Blender 3D Documentation Project</span></div></div></div></div><div><div class="h5">
<br><div class="gmail_quote">On Mon, Oct 2, 2017 at 7:06 PM, Tobias Heinke <span dir="ltr"><<a href="mailto:heinke.tobias@t-online.de" target="_blank">heinke.tobias@t-online.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hi Glen,</p>
<p>Hello and welcome. :)<br>
Fixing a todo is always a good start. <br>
</p>
<p>On the <a href="https://docs.blender.org/manual/en/dev/editors/node_editor/nodes/groups.html" target="_blank">node
group page</a>:<br>
I would suggest to add a proper paragraph about group in-/output
nodes first.<br>
E.g. multiple outputs: the last selected node will be used.
(currently at Interface > Panel).<br>
This can then be refer to in Group Insert.</p>
<p>The reason why the in/out nodes are created is to preserve the
outer links of the nodes.<br>
IMO it's better to simply start with a description how it is.<br>
Because later you might notice things you missed, like UI
conventions<br>
(multiple in-/output nodes for both materials and in groups),
hidden code related constraints & limitations...<br>
</p>
<p>Tobias<br>
</p><div><div class="m_2823388549611861073h5">
<div class="m_2823388549611861073m_6236606241402732995moz-cite-prefix">Am 30.09.2017 um 22:58 schrieb Glen
Larsen:<br>
</div>
</div></div><blockquote type="cite"><div><div class="m_2823388549611861073h5">
<div dir="ltr">
<div>First: As a start to my Blender documentation career I
would like to fill out missing sections relating to material
node editing. I don't see a list of section owners so is it
sufficient to replace a "Todo" with relevant text and submit a
patch? Any other coordination I should do?</div>
<div><br>
</div>
<div>Second: While quite familiar with node editing, I have come
across an operation that I've never used ("Group Insert") and
its functionality seems clumsy. It does what it says --- move
one or more nodes into an existing group --- but it adds
additional input and output nodes which forces further
editing. Certainly I could ask the module owners but are there
more appropriate discussion areas? Here?</div>
<div><br>
</div>
<div>Thanks for any input.</div>
<div><br>
</div>
<div>-glen</div>
</div>
<br>
<fieldset class="m_2823388549611861073m_6236606241402732995mimeAttachmentHeader"></fieldset>
<br>
</div></div><pre>______________________________<wbr>_________________
Bf-docboard mailing list
<a class="m_2823388549611861073m_6236606241402732995moz-txt-link-abbreviated" href="mailto:Bf-docboard@blender.org" target="_blank">Bf-docboard@blender.org</a>
<a class="m_2823388549611861073m_6236606241402732995moz-txt-link-freetext" href="https://lists.blender.org/mailman/listinfo/bf-docboard" target="_blank">https://lists.blender.org/mail<wbr>man/listinfo/bf-docboard</a>
</pre>
</blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Bf-docboard mailing list<br>
<a href="mailto:Bf-docboard@blender.org" target="_blank">Bf-docboard@blender.org</a><br>
<a href="https://lists.blender.org/mailman/listinfo/bf-docboard" rel="noreferrer" target="_blank">https://lists.blender.org/mail<wbr>man/listinfo/bf-docboard</a><br>
<br></blockquote></div><br></div></div></div>
<br>______________________________<wbr>_________________<br>
Bf-docboard mailing list<br>
<a href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a><br>
<a href="https://lists.blender.org/mailman/listinfo/bf-docboard" rel="noreferrer" target="_blank">https://lists.blender.org/<wbr>mailman/listinfo/bf-docboard</a><br>
<br></blockquote></div><br></div>