Dalija Prasnikar

You can find some videos on Embarcadero YouTube channel. Only sky is the limit. There are no limitations on what you can achieve, it is only matter of how much time you need to do that. At the moment the weakest point for Android development is using native 3rd party libraries that come in AAR form - packaged library with resources because integrating those can be painful process.

The annual fee is 99$. The higher 299$ fee is for large organizations that want to distribute their internal iOS applications without going through AppStore.

It looks like you are not logged into your account. Do you have an Apple account?

Maybe there is some bug in RAD Studio. I currently don't have my Mac connected so I cannot check the current behavior. What are the versions of software in your setup: RAD Studio, Xcode, macOS?

If it works in Tokyo you should report compiler regression to Quality Portal https://quality.embarcadero.com/ This is probably due to introduction of custom managed records that need additional handling and they broke record constraint that is basically constraint for value types. I had similar issue with variant records https://quality.embarcadero.com/browse/RSP-28761

Yes. That would also solve issues for people using trial version, bumping into some problem and then not having the ability to properly test trial version because they cannot install patch. I seriously cannot imagine buying something if I cannot properly test it. If I am already Delphi user and I want to upgrade, then maybe but in such cases I already have some other reasons for upgrading.

And this time it is fixed, finally. At least on Android... I didn't test other platforms.

You are correct. On Windows platform try...finally works fine.

For anyone interested in try...finally patch... it is still broken. I guess those "3 minutes" tests strike again...

You can join the beta if you are on active subscription. Most recently, betas were announced on Embarcadero blog posts like this one https://blogs.embarcadero.com/delphi-and-cbuilder-10-4-2-beta-invite-for-update-subscription-customers/ Invitation is also probably sent or announced through marketing emails. You will have to sign NDA and you are not allowed to discuss participating in the beta nor about any features, fixes or bugs. Above is valid for major release beta cycles and updated. Patches and hotfixes are commonly tested by smaller number of people because testing cycle is shorted and focus is on particular bugs. If you have some particular reason for testing some hotfix or you have some major issues using latest release, you can always try going through official channels and present your case. However, there is a catch-22 because you will never know whether some testing is in progress or not, and even when there is, you might not get answer to that question even when you ask directly (not in public). Next major release will be 10.5 and at some point you can expect posts (unless policy changes) inviting subscribers to participate for that beta. When will that be, nobody knows. For now you can just wait.

I am afraid that list might be too long... and it would require input from large number of developers. It all depends on code you have and what kind of workflow you have at any given moment and for which platforms you develop. What is good version for some people, might be utmost nightmare for others. And besides stability, there might be other reasons and bugs in the core frameworks which makes some versions unsuitable for some developers. Workarounds were usually move to another version and hope for the best. Without actually trying on your own code and working with some version, one can never know. Since Embarcadero opened up beta testing for larger audience, it would be good that anyone who can participate. The more the merrier. It is also important to start testing early, because some bugs if found too late in the cycle may end up unfixed. Of course, all that also does not guarantee final quality and release success, but it can be significant factor. Literally one person can stumble upon critical bug that would end up in RTM, and all other testers might miss it for one reason or another. It is huge codebase, and we cannot test and use all features thoroughly.

Yes. But you need to run application from Xcode at least once. I don't remember whether running the application is just for preparing the particular device for debugging - or you also need to run it for triggering creation of provisioning profiles, too.

You add that in Xcode (somewhere in Preferences). RADStudio does not have that option because it can handle only downloaded provisioning profiles. Any one will do. The selected one is fine.

The simplest way is to use Xcode because it will create and download profiles automatically https://help.apple.com/xcode/mac/current/#/dev154b28f09 Add your developer ID to XCode, create new application in Xcode with the same id your Delphi application has and run that application on device in debugging mode. Xcode will automatically perform the whole setup and then you just need to pick that profile in Delphi. You can also create and download those profiles manually, but it is longish process.

I am quite positive that some of the books you listed are not free. Even if you got them for free (some could have been distributed to Delphi subscribers as part of some marketing activity) that does not mean you are allowed to distribute the, Same goes for the books you purchased. You haven't bought right to distribute.

Be happy that you are not Cocoa (Objective-C) developer https://github.com/Quotation/LongestCocoa

Thanks! That means a lot 🙂 Since books covers both classic and ARC compilers, unifying memory management does not have huge impact on the book content. Only DisposeOf chapter and few references to mobile (previously ARC) compiler when it comes to reference counting for object references no longer apply. New mobile compilers now behave exactly like classic compiler, and memory management for that one hasn't changed. Eventually, there will be some book update, but not for now. There is not much going on in the memory management area that would warrant updating the book.

Sounds better.

Interesting... as non native English speaker, I guess I don't immediately see the difference. Above pairing generally makes sense. In this case, from my perspective TrimBeginning is extremely awkward to write.

Android API moved from such ambiguous methods and properties named left/right to start/end so following that rule it would be TrimEnd and TrimStart

As long as we have power, all is good

You can also try disabling package cache, it helped in my case. You need to edit registry key HKEY_CURRENT_USER\SOFTWARE\Embarcadero\BDS\21.0\Package Cache and then set the DisableAll value to 1. If it does not exist add new DWORD value with that name. But 10-12 seconds is really long time. Maybe something else is in play. If disabling Live Bindings and package cache does not help I would recommend filing bug report at https://quality.embarcadero.com/

Locks of any kind used as field in a class are meant to protect integrity of the data inside object instance, not to protect that instance from being destroyed. If you need to protect particular TMyClass instance itself, you will need to use some outer locking mechanism.

The most similar would be Delphi XE, but that is not a long jump 🙂 Every new version has some features and some differences, and you will need to tweak some code to adjust in order to benefit from those features. The more recent version you use, the less future tweaking will be required. From that perspective, probably the most stable recent version is Tokyo - 10.2.3. Rio - 10.3.3 is also quite usable, but it does have less stable debugger, and new IDE styling can cause performance issues on low end machines. All those versions have better support for using high DPI in your applications. If high DPI is not imperative for you, and you are less inclined to make huge jump, then XE7 is probably the most stable version in between. XE7 is also good option if your code uses class helper for gaining access to private class members, since that was removed in Berlin 10.1.

While 10.4.2 is a bit unstable (fortunately, my code does not choke it too often), going down to D2010 seems like overkill. There are many stable releases in between you can productively work with, and then move to 10.4.2 when patched.