Attribute Values pairs longest list rule issue

[mnaugle-tt]

Related to #21

Attribute Value pairs should work this way too:

[bhowes-tt]

As I mentioned in #23 , this feels like it's asking for trouble (or at least a lack of clear meaning) downstream. but if it is being requested in the interests of a less error prone UX, then ok, i buy it.

[mnaugle-tt]

@bhowes-tt if you don't like this or #23 then how do I create an attribute name called Z height and have a whole bunch of mesh faces have their own unique value? Right now I have to make a unique Key for each value.

[bhowes-tt]

@mnaugle-tt , assuming you want to select a face and see it's Z height attribute in the browser, each face should be it's own mesh.

If we laced it up the way you are asking, you would select the one mesh in the browser, and get a list of 'Z height' attributes in the element attributes dialog - one per face. Is that what you want?

[mnaugle-tt]

I would expect this to work:

Each face of the mesh is an individual item in a list, there is a single value going to [aN] and list of values that matches the length of the M items going to [aV].

So my next guess was to try this:

only being able to get there by grafting and using a repeat data component:

The first option is what I would expect as the best / right way to do this.

[mnaugle-tt]

apologies for what i now see as misleading initial example. i had removed all my other plugins when testing this morning so didn't have the ability explode that mesh. if you look at the this set of three code blocks hopefully that clarifies the issue better.

[bhowes-tt]

ok - that last one is almost there. replace the aN input with the single 'z height' panel and you'll be there i think.

[mnaugle-tt]

yes that works, but why not the first? the first is what i would consider 'standard' grasshopper logic.

[mnaugle-tt]

I see where you are coming from with this, fine to leave it as is. Just doesn't feel intuitive to have to either graph or repeat data especially in the instance of the first example (well actually the 2nd screen shot).

[anagpuyol]

I think this becomes more intuitive when you want to write more data into each mesh. Then, the way the data is written seems clean. Leaving it as is then