grazer or Mhx (if he is an admin?), don't feel obligated to read this. Just throwing out every "complaint", or constructive criticism, I have about each behavior and its properties/descriptions. I guess you could consider this a review. And a lot of questions lol. With that in mind, my aim here is to leave me and others less confused, maybe minimized forum posts for help, and some elaboration on behaviors. Grab some popcorn and sit back. In any case, here goes nothing:
Don't get me wrong, this one is pretty self explanatory. However, "trigger distance" remains vague. In what increment is this distance? Pixels? Blocks? Inches?
I also noticed you can adjust the bar, but you can't necessarily input your own value. Which further bewilders me. It still doesn't give me an indirect clue as to what increment this distance is referring to?
Its description isn't even in the documentation...I'll leave that up to that admins. And personally, I would like to know if this can be converted to a "tilt" behavior. (Temple Run for example.)
I very well understand that in order for the sound to be played, it be must be linked via .mp3 website. Now, if people have their own soundtracks to use, they aren't going to know where to go about this. Mhx once told me that you can upload the files to kiwi6 and copy the direct link. My suggestion; in the documentation, do make a note of that. Once people read that, I think it would leave us with little to no forum posts pertaining to that subject matter. (Such as "what site should I use", "how do I make my own .mp3 website", "why can't I just upload files", or "how much does it cost to upload to a .mp3 website?" See what I mean? But hey, that's my perspective.)
The "max age" property. Although this one I do understand that it'd be best to play around with, it wouldn't hurt to know in what time length the object will disappear.
Ok, this one you may have to play around with. My suggestion, for the sake of time, would be to have the ability to attach the object within the object editor lol. Good idea, no?
Well, there's an "output". Isn't it pointless? I mean, once the object is destroyed, it's not going to fire any more triggers. MORE IMPORTANTLY; You see, leaving that output there will lead people to believe that triggers can be fired off after the object is destroyed. That is clearly not the case.
(*Note, due to my analytical mind, feel free to skip this one. It is quite long.) In my opinion, this one needs much elaboration. Hey, "position", that sounds simple to use, right? Of course. But then when you figure out what kind of component to connect it to...you don't know how it's going to behave, nor if it's even needed for that matter. I'm just left with "position". So therefore, my question is; position...in what respect? Ok, maybe that can't be answered, so let's go back to what I previously stated. "You don't know how it's going to behave, nor if it's even needed for that matter". Let's take a deeper look at what I'm saying:
So let's say I want an object to move left on the x-axis. Let's do this:
Always - number (5) - (x) impulse ... but hey, it moved right! How do we fix this...of course, the "forward" input in impulse! So let's go to the object itself, and change the "forward" to left. Let's go back to the behaviors:
Always - number (5) - (forward) impulse ... problem solved! But hey, couldn't I have used the position behavior? What is it? It says...set's the object's x/y position. Hmm... Let's take a look at it real quick. We have:
***Now, before I proceed any further, I have some questions about the above. There's a plain (x) and (y), and a...well that's wierd, another (+x) and (+y)? And by another, I mean that (x) and (y) is already positive, no? NOW, judging from the fact that flowlab seems to be focused on side scrolling, it's safe to assume that the axis is programmed. Meaning, there's a -x (left), +x (right), -y (down) and +y (up). So all in all what is the meaning of (x), (y), (+x), and (+y)? It seems to be based on the axis. Ok, let's assume the (x) and (y) are negative. I still want the object to move left. Let's try it.
Always - (number 5) - (x) position.
The result; the object disappeared?! Alright, fine. But ... position seems to be similar to velocity/impulse, given the "reset speed on update" property. On top of that... on what "update"? What are we updating lol? Like, is the initial trigger supposed to be always?
Even if so, if I wanted to make something move in the negative direction, I think it'd make sense to make the number a negative.***
All in all, I'm beginning to wonder if this is a necessity, or beneficial. If I want an object to move in a specific direction, could I not customize that using velocity, impulse, and/or their x, y, and forward inputs?
I know, this one is easy. For the sake of time, rather then using a number, have the percentage within alpha? Like an adjustable bar?
Well, the same thing I said about alpha. But also, there's something in the documentation that was absolutely excellent about this one:
"Out outputs the new size." You see what you did here? You indirectly told us to put the number before; inside the "%" input. I mean that would make sense but...still.
A while ago, I did try to turn off all of the object's behaviors. It didn't work for some reason, so maybe check on it for a bug? Maybe it was just me. More than likely.
Just a reminder; don't forget to make the ability to delete frames, as I saw in one of the forum posts...
Within the properties, we have:
From current object:
From selected object:
Nothing seems to be an issue...hey wait, From "current" object and From "selected" object sound the same. Ok, so they are... Probably nothing big, let's just stick with "current".
Actually, at the time of writing this, I clicked on "From selected object" to see what would happen. To my surprise, more options suddenly appeared. I was not expecting that, nor did I know it existed. My suggestion; keep the extra options there, but keep them highlighted in gray and unusable. That way, if people need those options, they will educationally guess to click on "From selected object" to use those options. They sound very similar in my opinion.
Mouse click and Mouse move:
Just a reminder; I would suggest to make a note in the documentation that both are converted to touch and drag on the iOS.
Ok, that is all I have for now. In any case, I hope someone read this. Hey this seemed to be a very negative post, this needs some positivity...flowlab is an absolutely awesome program, I am surprised there's a free trial for it. Compared to other iOS programs, I'd have to say this one is best and easiest to use. Especially the object editor. Thank you for that, it gets old after creating your own images and watching them distort in other programs lol.
Throw in the input, I am very curious about what yall have to say.