Leaderboard

ICS includes forked version of SuperOject 1.2 so that ICS can offer the same JSON support on all platforms, It's not the latest version, since ICS already has time zone functionality that got added to SO. Also removed TSuperWriterSock since did not need it. I've added better TDateTime support, reporting JSON parse errors and other minor fixes. Fully compatible with D7 to D11.0. The unit's only dependency is an ICS utility unit, so it can be used without anything else. Angus

Just got the tournament mode working! Now it's SpaceBallz Tournamentz!! SpaceBallz Tournament server is a 3d windows app as well, maybe the 1st 3d server, idk.. Just a very simple thing, used ICS and sever is also a leader board that displays top 12. Now you can re-purpose that old windows tab collecting dust. The game is using Indy, tested on my cheap android 10 tab that's permanently wired into my delphi.. Not perfect, just fun stuff.. Took me a bit, was busy busy and it may show a bit in the code, as i rated it pg-13, for language and drug use.. edit, lines 117,118 in uSpaceBallzData pretty much sums up my existence and i bet you im not alone there.. 🙂 have fun.. ~q

Thank you, Dave! Changing %minSdkVersion% value in AndroidManifest.template.xml in combination with adapting NDK settings as per your (quoted) article increased the number of supported devices greatly! I tried platform android-19 fist, but that threw an error, so I settled with android-21. It should be stressed that changing only %minSdkVersion%, as suggested by Philipp, does not do the job, as this "fakes" an environment which strictly doesn't exist. My substantial main error though was, that I deleted target platform Android 32 bit from project manager in app version 2.10, caused by my misunderstanding of Google's policy, that apps have to support 64 bit from last August on. That does NOT mean, that app bundles should not also include a 32 bit package! Older devices obviously only accept 32 bit apps. Now, with re-installed Android 32 platform and android-21 NDK platform settings, I am back to 17.463 devices. 🙂

You could use a database transaction. Begin the transaction before printing and commit the transaction after printing. Roll the transaction back if printing failed. If a program crash occurs while printing or before the program crashes, the transaction will automatically rolled back.

And there I am, still hoping for that day to come

True. Somewhere back in time, I thought I had heard or read this and well, it made sense (to me) and a quick test of this one particular case in one particular version of Delphi confirmed my thinking but you're right, it certainly does not prove a rule. The much, MUCH better way is to just avoid writing obscure code in the first place.