How to use "For Each" tag loop on each object
-
@iTap-Development THANK GOODNESS I DID NOT LOOK AT THAT PROJECT.
I'm already confused enough about arrays and spawning and IDs in this clusterfuck of an environment.
Not having references and instances is doing my head in.
-
@iTap-Development Again, just explain WHY it's better. You've done the hard part, explaining how it works.
-
@iTap-Development and tell me why my way is inferior or suboptimal. Cause my way works. And circumvents the problems I've had with hyperPad so far.
-
@Deeeds I did explain how it works.
-
@iTap-Development explaining how something works, yes. I know. I acknowledged that you did that.
WHY is your way better?
Why is my way lesser?
-
@Deeeds simply that your way seems like more hassle, and uses more behaviors than are needed.
-
@iTap-Development On the contrary. My way is far less hassle.
It's a factory based on the Index. That's the first point I made, that my way is lean, mean and SIMPLE!
Pump out units, use index as ID by virtue of the position property, no communications required, no array of IDs required, nothing. Just pump them out and stamp them with the index via position.
AND QUICK!.
-
@Deeeds ok! To each there own. Or should I say, for each? Did you check out the project?
-
Oops I forgot To post it!
http://bit.ly/2jKzU7X -
@iTap-Development How do I get to this forum in the App?
-
-
@iTap-Development Nevermind, found it It's the ULTRA thing, ridiculous helvetica nueue uber thin text at the bottom.
Another thing that passed focus group testing, I suppose.
-
@Deeeds get your eyes checked, maybe?😁
-
Why am I not surprised?
-
@Deeeds you can’t click the download links in the forum. You have to open in safari.
-
@iTap-Development seriously?
What year is it?
-
@Deeeds aww get over it. Just drag the link. iOS 11’s wonderful drag feature!
-
Well, does it do what you wanted?
-
@iTap-Development Do you mean the wonderful features of iOS 11 that are NOT implemented by hyperPad?
That's not my point. although it is also a valid point. They should have implemented all the iOS 11 goodies for this app long ago.
My point: somebody permitted that connection error message to be shown in these circumstances, which is both misleading and useless.
-
@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!
