@Patrick123 which project? I think you mentioned the wrong person

Posts made by Kamdroid
-
RE: 1.26 Beta
-
RE: 1.26 Beta
Really sad. Hope you can release an update soon. I think I've been waiting like 6 months 🙁
-
RE: 1.26 Beta
@Murtaza @Hamed I sent you an email a few days ago, but if you didn't get it:
Can you make a TestFlight version which is just the stable version of hyperPad with the bug fix for iPad Pro UI/global layer positioning bug (so people without beta can play my projects)
That's the only reason I'm stuck using the beta, but it means I can't release or update any projects since most people don't use the beta.
-
RE: 1.26 Beta
@RobinsonX thanks. In the past I've always just used get and set attributes, I had no idea
-
RE: 1.26 Beta
@Hamed can you confirm if "set input field" behaviour exists in the new beta (or was it renamed)? I can't seem to find it anywhere.
-
RE: 1.26 Beta
@Murtaza still would be nice for some basic features to be added. Such as, string manipulation behaviours (if contains, split text, regular expressions)
Also an "evaluate equation" behaviour to dynamically do equations (e.g.
5 + 5 * 2
) -
RE: Execute and wait for behaviour bundle to finish
Since I'll be using the "calculate result" function multiple times in different places, I think the best option is:
- Use broadcast/receive message. When using "calculate result", supply a parameter that says the name of the "receive message" key to activate (basically a callback function)
Which is similar to the separated behaviour bundle + "behaviour on" technique.
If I could dynamically supply the name of what behaviour bundle I want to activate, then I would choose to do that, since having multiple "receive message" might have a tiny performance impact.
-
Execute and wait for behaviour bundle to finish
Is there a way to execute (behaviour on) a behaviour bundle, and wait for it to finish running before continuing the main code.
Example:
-
RE: Xcode coming to iOS 14
Is there a reason why apps like Codea, which have fully featured Lua programming are allowed, but hyperPad can't?
-
RE: Scene/Global UI positioning glitched on iPad Pro
@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:
-
RE: Sports Challenge! Win an iPad Air!
@Hamed I'll give it a try. How do I get the beta?
-
RE: Sports Challenge! Win an iPad Air!
A month later, the update still isn't out. I'm guessing the update will be out weeks after this challenge deadline.
Is it really that much of a hassle to do an update just to fix the UI positioning bug?
-
RE: Sports Challenge! Win an iPad Air!
Maybe you could give me a beta version of hyperPad, just with the UI positing fixed.
-
RE: Sprite sheet splicer
@Stanica A feature that could automatically detect the spritesheet dimensions would also be really nice, like detecting via the transparency space between sprites
-
RE: Sports Challenge! Win an iPad Air!
@Murtaza Hope you release the UI position fix soon. I know you said gameplay is more important, but adding UI would help me visualise it a lot better.
Personally, I think you should of fixed UI position glitch before starting a challenge.
I do want to try this challenge, so I hope you release it ASAP.
-
RE: Sports Challenge! Win an iPad Air!
Would be nice to fix the incorrect UI positioning on iPad Pro first. I'll probably have to pass because of that
-
RE: Attaching comments to objects
@SplitMindGaming This seems to be an actual bug. When using behaviours like collided, if comment is attached, it will trigger the collide only one time and stop working.
Video:
CommentAttachCollideBug.mov -
RE: Guys, I need help.
@EpicCakeGameMaker Share the project which has this issue. I'll take a look and see, otherwise it might be a potential bug
Worst case, making a custom jump behaviour is fairly easy and should let you fix this problem.
-
RE: Scene/Global UI positioning glitched on iPad Pro
@Hamed @Murtaza Any estimated time when this will be fixed? I'd appreciate a fix ASAP since this is the reason why I can't work on any projects.