How to use "For Each" tag loop on each object
-
If you can, I'd greatly appreciate an explanation of Value Type arrays in hyperPad, from your perspective.
-
@iTap-Development Yes, I found it before you sent me the project.
I was writing about it before then. Look at the timeline of events.
-
@Deeeds I don’t know what you mean by “value types”.
But that’s not the issue. The issue is that you thought FOR EACH couldn’t loop through objects on a tag and get there positions and add them to an array. When I made a project proving they could, you easily saw the user error. The point is, if you shared a simple project demonstrating what you thought didn’t work, I could have identified the user error 6 hours ago in stead of posting so much!@Deeeds said in How to use "For Each" tag loop on each object:
@iTap-Development You're doing the exact thing I am. The difference, I assumed the default type of array in an Array Modifier Behaviour, in hyperPad, would modify hyperPad's native arrays. I was especially sure of this because it's been named a "Value" type of array, which would be, in most all other uses of the English language to describe anything to do with modifying arrays, the type of array that stores values. And it is the default setting of the behaviour that modifies arrays within hyperPad.
SILLY ME !!!
Should have known that the wording would be wrongheaded and the default choice the least intuitive and least useful, and most peculiar possible.
Made far worse by the fact that it takes in an array to modify, and then requests the choice of modification and the value to be provided. Looks exactly like what's needed, normal and to be expected.
Again, Silly ME!
This post is where you first said you new what was wrong. I posted the project before this.
-
This is the post where I explained EXACTLY what one part of the problem is, long before you sent the project:
-
@iTap-Development in between then and your project sending, I then explained, as politely as I could, why word choice is important in a tool like this, to the person I assume is making these choices:
here
https://forum.hyperpad.com/post/4367
Because I don't want anyone else having this same experience!
-
@Deeeds look at when these posts were posted!
-
Dang it I cropped it off let me repost
-
EDIT
you made your post and hour later. -
@iTap-Development Scroll up. The posts are in chronological order. You'll see what I'm seeing. That I'd identified the root cause and fixed the problem, and then gone onto describing the reason for the confusion, and why it needs to be alleviated, long before you posted your project.
Thank you for that, it confirmed we were doing the exact same thing. But I had already found and isolated the problem. And begun ranting about the naming and default choice in the behaviour... etc.
I'm not into suggesting words yet, but that will be next, if and when @Murtaza or you can explain why/what/how/when/where of arrays of type "Value" are and do in hyperPad.
-
@Deeeds if you had it figured out already, why did you look at my project then? Regardless of when we posted, if you had sent a test project, it would have been solved IMMEDIATELY!
That’s the point. -
@Deeeds show me where you “identified the root cause before I posted the link”.
-
It's the ******* (curse word edited out, use your imagination, add rage... then...) ARRAY modifier of type VALUE!!!
-
And I'd already identified what was probably going to be the cause of the problem:
It's counter intuitive and requires additional actions to setup "correctly".
-
@iTap-Development said in How to use "For Each" tag loop on each object:
@Deeeds if you had it figured out already, why did you look at my project then? Regardless of when we posted, if you had sent a test project, it would have been solved IMMEDIATELY!
That’s the point. -
@Deeeds Why do you always refuse to share the project with your issue though? It only takes a couple of seconds.
-
@Kamdroid exactly!
And then the problem could have been solved in two posts if he had included a project. Now this thread is at 63!
It’s like he wants help, but then refuses it. -
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?
