Add "Change all to Read/Write" to bundle/unbundle functions

[JDinkins]

T

This idea could be applied to the bundle/unbundle primitives as well. Wiring may be an issue though (may produce broken wires).

This idea would be moot if the cluster functions were redrawn like property object functions (even better idea...).

-Jerry

[JDinkins]

Hrm, my post is incomplete?

here is the picture, anyways

[Mr.Mike]

I'm not a fan of this idea.  First off Bundle requires two wires of the type you're bundling and Unbundle only requires one.  It's not clear where that extra wire is going to come from / go to.  Also, anything connected will break.  It seems to me that Change All To Read belongs with property nodes because there's also the option to change an individual to read, and change all is an extension of changing one.

It doesn't seem to me that you'll often need to change from reading many items in a bundled type to writing.

[JDinkins]

Two options:

1. Instead of "Change all to Read", offer "Replace with bundle/unbundle"

2. Offer an object like property nodes, but for clusters. (<- this would be awesome)

I say this is a productivity issue because it's time consuming when placing new bundle/unbundle by names with large clusters (many types of non-uniform data). Most of the time, I prefer to copy an existing bundle/unbundle by name to avoid re-selecting the necessary elements.

[elset191]

---

@JDinkins wrote:
2. Offer an object like property nodes, but for clusters. (<- this would be awesome)

---

 Property Node Style Bundle and Unbundle Element

[X.]

To Mr. Mike: Here is an instance where the original suggestion would help.

==> Right-Click>>Replace by "Bundle By Name"===>

As you can see, you don't (always) need to worry about what to do with the source wire for the cluster type.

Second, the current replacement is rather stupid. It takes the "first" cluster element and replicate it. I am confident that this is the "intended" behavior (in the sense that this is how it has been programmed).

I don't think I am the only one that this is not the "expected" behavior.

Kudo from me.

[Darren]

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined. 

[X.]

Declined is a shame. This is a good idea and should have got more exposure. 

[Darren]

My mistake, this idea is actually In Development.

[elset191]

What a rollercoaster this is