How to use "For Each" tag loop on each object
-
@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!
-
@Deeeds value arrays can be dynamically created and used. Using the behavior setting means you have to select a premade array.
What’s so weird about that? -
Can you explain HOW this works? What it does?
Step me through an ideal use case of this wonderful, dynamic array functionality.
Write like speaking to a child. Not childishly, just as though you're explaining it to someone that comes from other worlds, not one where knowing hyperPad is normal.
-
@Deeeds ok.
Say you want a shop. You could have an array of categories for the shop. Say you want unlimited categories. Each index in that array would be a dynamic array of items in the category. -
@iTap-Development So you're talking about accessing nested arrays?
If I get that... then I think... this is way to get around the lack of referencing in hyperPad?
-
@Deeeds yes that is what I’m saying.
How is it a way around referencing? Sorry about my not understanding your terms well, I don’t know much about “normal” programming. -
If you've got referencing, you don't need do all this dancing through hoops we're doing to create and ID objects.
You have a virtual "name" for each object, and can call on them at any time and say:
FatDog06.fetch(yellowBall)And each different dog you can tell to do different things.
Or get information from:
FatDog09.reportDistance(inMetres, fromHome)That name, for each dog, is a reference to that dog.
And you can pass the name around.
So you could tell your buddy to wash a particular dog:
Buddy01.wash(FatDog007)=================
For @Hamed, who is (I think) probably working in Objective-C, messaging looks more like this:
[Buddy01 wash:FatDog007]But the capitalisation isn't done like that in Objective-C, I kind of vaguely remember.
The real problem, I still don't really understand what Value Type arrays are in hyperPad, or what problem they're solving. I'm not sure how normal arrays couldn't/shouldn't be used to solve your problem of the store and categories of objects, etc.
-
@Deeeds said in How to use "For Each" tag loop on each object:
@iTap-Development Again. There are OTHER things I'm doing, that require this functionality.
This isn't just one problem that needs to be solved. But this makes for a great example to demonstrate the conceptual capability, which in turn, if it works, should provide artistic freedom of some description.
So, no... not going to share a project.
Instead, show me that it works.
I've found so many things that don't work that I'm far beyond doubting myself, and already eliminated any possible user error on my end.
ly.
The only things left are:It's broken
or
It's counter intuitive and requires additional actions to setup "correctly".
Show me it works. I don't think it does.
Do you see the need for sharing projects yet?!
You were “far beyond doubting yourself” and had “already eliminated any possible user error on your end”, and that there was no need for a test project.
If you had shared a simple project, someone could have easily found the problem.
