How to use "For Each" tag loop on each object
-
it only takes a couple of seconds
No. this is absolute nonsense. Patently false.
If it only took a couple of seconds, I'd sometimes have done it.
Save my project... several minutes, sometimes as much as minutes.
Recreate the issue in another project that isolates this problem.
Several minutes, depending on the problem. And there's no way to copy anything from one project to another...
etc.
And, secondly, there's no need, in this case or any of the others I've posited so far.
A brief scan of what could go wrong isolates where someone might go wrong.
I even speculated about it before I figured it out, and got that right.
For someone familiar with the process it must be much more obvious where the tripping points are.
....
A better question, why aren't there isolate examples of using every single feature of hyperPad if it's so easy to share?
-
During the building of your project you changed the type of array.
Why did you do this?
Can you explain the differences between operating on a Value Type array with an Array Modifier versus operating on a Behaviour Type Array?
@Kamdroid can you explain the differences between these two types of arrays and why operations of append do not work with one, but do with another?
Interestingly, there's no difference in getting values from either type.
So, the question becomes... is something about the Array Value Type broken? Should it behave in the same manner when amending values to an empty array?
-
@Deeeds all I did was choose to use a pre-made array since it’s easier if you don’t need anything nested or whatever. The difference? On a behavior type array, to modify you just need to select the array behavior you want to modify....simple.
On the value type array, unless you put in an array for the value, it’s making a new array. And then to use that array with anything else, you have to use that modify array’s output.
I don’t know if if this is what you were doing, but you can’t like type the name of a behavior array in the value type input field. -
@iTap-Development Are we looking at the same thing?
-
@Deeeds you tell me!
-
@Deeeds can you post a screen shot? Or is that too much like a project?
-
@iTap-Development No need for the attempts at asides. Don't poke a bear, etc...
The question remains the same, why doesn't this work?
-
@Deeeds if you want to set it up like that, you’ll need to SET the behavior array to the modify output. When you drag the behavior array output into the value input, it basically is only a copy of what the behavior array was. It’s not actually modifying the behavior array. Which is why, in this case, you would modify as a behavior type array.
-
@Deeeds if that doesn’t make sense, send it and I can show you😄
-
@iTap-Development Just explain, where is the modify Array output?
-
-
@iTap-Development So I'd have to replace the array to do it this way?
-
@Deeeds what do you mean?
-
@iTap-Development The output from this operation, using the Modify Array in this way, is going to be a whole array, right?
-
@Deeeds yes it would. Which means you would have to set the behavior array to that output.
And at that point it doesn’t make sense to do it this way. -
@iTap-Development That's what I mean, you're overwriting the array. Right? Can it be done? Does it work?
-
@Deeeds yes, if you set the modification to SET and actually choose the array behavior(not how you did in the screen shot) it will overwrite the behavior array with the modify output.
-
@Deeeds but like I said, there no point doing it that way. In this case.
-
Can you explain how you came to understand that Value Type arrays are copies of the original?
-
@Deeeds played with them for an afternoon when they came out. Probably asked a question or two.
It’s not that complicated.
