Forum Replies Created
-
Posts
-
$50 USD sent with paypal
Could it be that your XCode project doesn’t have launch screen images for your device resolution?
https://developer.apple.com/ios/human-interface-guidelines/icons-and-images/launch-screen/
From what I understand, iOS uses them to determine if your app supports native resolution of the device, and if not, the OS will scale your app (and hence the app will get some scaled width and height info instead of the actual pixels).
In Mark’s defense: this nagging about the language name really has to stop. There is nothing wrong with the name, it isn’t any worse than Python, Rust or Ruby. I personally like it more than the Blitz- prefix, but then again it is just one guy’s personal preference, so who cares.
Besides the language itself, what’s really needed for a new semi-professional user is decent up-to-date documentation and a reasonably feature-complete IDE. Monkey X had good docs and it had Jungle. Ted2Go is not Jungle yet, but it is getting better and better, and it is cross-platform from the start, which is something Jungle never had.
And let’s get our expectations checked against reality – if we want to even talk about Monkey 2 becoming something more than what it is, let us all go to Patreon, and pledge a significantly larger amount than those paltry sums we have there now. Put your money where your mouth is, or please kindly shut the f#*k up
I noticed this little problem in Windows 10 (4K display, system zoom 225%, Ted2Go compatibility settings set to Override High DPI scaling – Application). After clicking Window-Zoom in several times, everything seems to scale nicely and looks sharp, except the line height in autocomplete list is not adjusted and the lines overlap like this:
Attachments:
For what it’s worth, as long as I can still make 2d Android apps compatible with gles2 devices, this decision doesn’t affect me. Sorry for the selfish point of view: I don’t have the expertise to look at the bigger picture.
Still, I’m sticking with ‘no’ for now.
I understand. While Monkey-X WinRT target proved to be useful, I would much rather have in-app purchases for the three mobile markets I mentioned, if I had to choose between them and a Windows mobile target. For now I’m still using Monkey-X for production, and I cannot even consider switching to MX2 until in-apps are supported. I think Xaron is in the same boat, judging by his posts.
Good stuff! Purchased. Now I need in-app billing for Google Play, App Store and Amazon and I’m all set
Universal Windows Platform app support with in-app billing would be too much to ask I’m afraid
@codifies #Regions are foldable. I personally find them quite useful, but that’s a matter of taste. They are supported by Jungle and Mollusk.
@nerobot Sounds like you want to build a new Godot
I might be wrong here, but it looks like the “easy 3d for everybody” niche is occupied by Unity, and it is next to impossible for a small development team, let alone one person, to compete with that (I might be wrong here – Mark is quite a capable man).
I took a quick look at Godot. For me as a user, it looks like what MX2 could’ve been given enough time and development effort. It has a development toolset build around the core, and it’s all neatly integrated in one package. Not as 100% plug-and-play as Unity, but more interesting for people who like to tinker (kind of like Windows vs Linux). For MX2 to get to this level, there should be, as nerobot put it, a lot of enthusiasm (which is the domain of the young and the unmarried
With whatever experience and codebase I’ve accumulated in Monkey, I think I’ll stick with it for 2017. It meets my modest needs.
