How to use "For Each" tag loop on each object

Deeeds

The last remaining potential problems?

I was doing the For Each loop on a UI element (a label) and thought this might be a problem, so I put it on a normal object. No change.

I was searching for tags on complex objects that do a lot of moving. Put tags on simple objects and removed the complex ones.

But no, that's not it.

It's the ******* (curse word edited out, use your imagination, add rage... then...) ARRAY modifier of type VALUE!!!

In the entire rest of the known universe, that's what we're doing. Modifying an Array of Type Value. It's an array that stores VALUES!!!

Meaning... it's an array of type Value!!!!

WTF*

*The decision behind this naming convention was probably focus group tested

Bah.

I have read the documentation again, and I still cannot figure out what an Array of Type Value actually is if it isn't an array of type value. Something to do with JSON values, but I'm not sure JSON means what they think it means, or what their intention was with this absolutely ridiculous nomenclature.

iTap Development

@Deeeds ok, this is how I did it in my project. Basically, when there is a “request” for a spawned object(in this case the mate wanting a buddy), the wanted ID is added to an array. That array holds all the requests. The array then takes the first index(that would be the oldest request, assuming you append the requests) and spawns the object and then the object sets its ID based on the value in the array, then triggers the array to spawn the next object. But don use the project I gave the link for, because I just realized that it isn’t right....at ALL! I need to fix it.

I’ll make a loop example.

iTap Development

@Deeeds so you want it to loop through objects and add there positions to an array? Right?

Deeeds

@Murtaza There was a movement to define and steadily and increasingly make a meaningful and less ambiguous and scattered approach/definition to use of the word "Type" in programming over the last few years.

The result is this:

Value Types and Reference Types on the one hand, and the type of objects (lower case) on the other.

Value Types get copied on assignment. Things like functional programming rely on this, almost in exclusivity, it would seem.

Reference Types we've already discussed, are those that point to the original... a reference.

Within reference Types there is the type of object, as defined by its class. Notice I'm using a lower case t for this definition of type.

I'm generally and genuinely curious.

What is a Value type of array in hyperPad. I know you say it's a JSON something... then your writing gets lost and I lose any hope of understanding what you're on about.

JSON arrays are, generally speaking, of only one type of object. Be it ints, strings, whatever... so not altogether dissimilar from any other array in most other languages that are not JavaScript, and those few really dynamic environments where an array can contain a lot of different types. This is, if I remember rightly, one of the only real reasons JavaScript needed JSON arrays, so that it could be sure of what type was in the array, and only that type.

I don't really get what you've done here. Sometimes your Value type array works as a normal array might. Other times it does things I can't explain, or simply doesn't respond. And I'm sorry, I don't understand the documentation on the matter, at all, thin as it is.

iTap Development

@Deeeds here! http://bit.ly/2jKzU7X

Deeeds

@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.

Deeeds

@iTap-Development Again, just explain WHY it's better. You've done the hard part, explaining how it works.

Deeeds

@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.

iTap Development

@Deeeds I did explain how it works.

Deeeds

@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?

iTap Development

@Deeeds simply that your way seems like more hassle, and uses more behaviors than are needed.

Deeeds

@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!.