@Kamdroid Just after doing some testing, for me the game seems to always actually wait for the calculation to finish before moving on to the next behaviour under behaviour on anyway, even when calculate result had loops.
@Kamdroid You could still Share it to send it to somewhere external (e.g Apple Notes app if you have it, or HyperPad Viewer) then just send it straight back to hyperPad and rename it. Annoying workaround though.
@Murtaza The beta has fixed this issue. The only thing left is just a non-important visual glitch, where the hyperPad menu button still shows on the wrong position:
@SplitMindGaming You can make an animation in one folder already. When you click import assets you have the ability to select animation, it will create an animation of graphics that you have selected. And you can also make it when you keep touching an existing graphic, it will make an animation inside the existing graphic and there you can have multiple animations.
Sorry to see you go! You've been a part of the community for a long time, so hopefully you can find some time to pay us a visit :).
Also sorry that you're feeling discouraged on waiting for new features. We have a release cycle of 4-5 months for major release updates. We do this for a few reasons.
Users don't update as often when we do quicker updates. They often skip updates. This causes major issues, or false bug reports and slows down our progress and also makes them have a bad experience since they're having bugs that have been fixed.
If we do major feature changes very quickly, this could potentially cause issues with existing projects. As you all have probably realized when creating your own projects, fixing one bug or adding a new feature adds 10 more bugs ;). While the hub and public facing part of hyperPad is in-active, we do have schools and "pro" developers that require this type of stability. Sudden changes are bad for these users, and since this is where the majority of our use-base sits, we have to cater to their needs.
Most often there are work arounds for bugs. For any bugs that are critical, we usually release an update a month after the "big one". And then subsequent critical bug fixes after that.... As long as they are reported. We have a major problem where a lot of bugs do not get reported.
Now, that being said there have been major underlying changes with the hyperPad behaviour system (as you've noticed). We've shifted from developing major features to developing tentpole functions that will support the future. This means we're building the core support and functionality. While it's not pretty, it does make the behaviour system more robust. By adding things like arrays, dictionaries, object references, and attributes we've opened the the behaviour system to be extremely powerful. You may not realize it, but you now have the freedom and power to create almost anything in hyperPad (sometimes a bit tedious, I know!)
For example, while developing some of these features, one of our previous engineers essentially created a behaviour system within hyperPad....
Once these tent pole features are in place, we'll focus on simplifying them and making them more accessible. This means adding things like functions, robust sharing and collaboration.
Any ways, I don't want to make excuses (we know we've been slow, especially with the last update), or change focus on your post. It was great having you part of the community, and we really do hope you pay us a visit from time to time!
@murtaza do you think importing and exporting behaviours as json be considered "code" by Apple? I have no idea how strict they are with that but there are apps that let you run python and stuff like that.
I still want a run code behaviour 😛
Apple is very inconsistent with their rules. Often times if the reviewer likes you, they let things pass.
They have loosened some things up a little when it comes to this kind of stuff, but still extremely strict.
I'd love an execute code behaviour, but I doubt that apple would ever let us have that. Thats why we had to move it outside the app with exported projects and broadcast message behaviours. (broadcast message can execute objective C or swift in xcode)
Where apple gets very strict is when it comes to sharing.
While reproducing I noticed that the inaccurate touch area seems to be corrected if you slightly move the effected behaviours. Perhaps it's because I commonly add a new behaviour in the middle of two and then don't need to move it after connecting them up.
Also encountered a little bug where the left-side behaviour list for any of the categories wouldn't show up until re-entering the object's behaviours