How to use "For Each" tag loop on each object
-
@Deeeds for you that’s never?
And htis is this NOT the time and place?! -
@Deeeds this is exactly when you should be sharing projects!
-
Read through my rant about the Value Type being named wrongly, the default choice... etc...
It wasn't user error in this case...
It's horrible UX, terrible documentation and TRULY despicable choices of nomenclature and default "behaviour", all to circumvent a temporary problem, the lack of referencing.
-
@iTap-Development You haven't read the path to discovery I went through, that everyone else will need to go through, too.
It was painful because of the documentation, the default choice, the naming conventions and the reasons for this scenario.
You're not getting the points I'm making.
And I'm not willing to wait for someone else to help me when I should be able to solve these problems by reading about and using the tool in front of me.
This is about FAR MORE THAN ME!!!
-
@Deeeds I don’t need to read your rant. Read the post I quoted. You said all of that about the for each not working.
Had to edit...i wasn’t paying attention to what I was typing lol 🤦♂️
-
@iTap-Development You only need to read through something if you're going to try to stand behind your claim that this is the right time to share a project, and you're going to be faster than I am at finding what's going on, and can then explain to me the process by which YOU discovered and then understood THIS problem.
Can you do that?
-
@Deeeds are you saying you found the problem first? I thought my project is what showed you? And It wasn’t a problem! It was YOUR user error, which is why sharing a project so I could look at it was needed. It would have been easy to see why it wasn’t working.
-
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".
