@hamed this locking, from the reliance on CADisplayLink falling behind, is also why hyperPad drains batteries. It's 100% CPU usage essentially looking/waiting for the next CADisplayLink, but which isn't enough for it to get back in front of itself. A loop just flogging and thrashing the system, needlessly.
@thecheater887 I think the difference between behaviour on and execute behaviour is that execute behaviour won't run the behaviour if it is off.
Like Kamdroid said, broadcast and receive are similar to what you're suggesting, allowing you to send an array or dictionary and use it in child behaviours.
Edit: fixed typo.
Ohhhhh I see what you're saying now.
So with your example, players are consuming content... They're playing a game. With hyperPad it's more to it than that. They have to actually use the app and create something. So right away it requires more involvement.
So a survey is ok in some situations. But depending on the stage of the beta. It's mainly use the app. And test the specific functions we've changed or features we've added. But really, we're just asking you to continue using the app and if it's broken then report it in the beta section of the forum (where you only have access to if you're taking part of the beta).
Also with the betas we're selective of who can take part. Because sometimes they're trying out new advanced features that a beginner wouldn't know how to use. Additionally. with the betas you can't share to the hub. So this adds an extra issue for some people.
The major issues we had with betas is that users were excited at first, but then they either don't install the beta, or don't install the following versions so we don't know if their issues are fixed.
As for incentives, we did reward all beta users with "Developer" tiers.
You're right that the betas feel like it requires more dedication. And I think only users who are experiencing issues will take it seriously enough to provide their feedback.
@deeeds Yes you give some constructive criticism, but sometimes you're not constructive, and you come across as very aggressive and judgemental. You're saying hyperPad or Murtaza and Hamed do nothing for us? What are you saying, that every time Murtaza and Hamed say they're working on the next update, that they are just lying? Lol let's add a new forum post called "Arguments with deeeds" at least then it'll be a forum topic that will actually stay on topic. 😝
@aidan-oxley a while back I had a timer of 0 moving an object, and had to use 0.01666 too.
I don’t know if this is right, but when I looked it up I found that it had to do with movement on a 0 timer not always being in sync with the frames.....so like the object might move twice between frames and then once between the next frames. Maybe just if the the fps fluctuated.
But if the timer is 1/60 or 0.01666... It supposedly keeps the movement in time with the frames.
Not sure if this is actually true, but it seems to work.
@deeeds said in Delete tags and use them only in one scene:
@gamecrazy prob 2 bz bc tradn
Or you know. Busy coding. (Actually don't even know what you're trying to say?)
Honestly, any date @hamed gives should be ignored. He's not the best when it comes to estimating times.
Looks like your connection to hyperPad Forum was lost, please wait while we try to reconnect.