Leaderboard

Using '' is the way to go. It works since pascal days, and compiles as a `nil` pointer. Using `EmptyString` or `string.empty` does not make any sense, in the pascal language context. There is no such thing as a null string. An empty string is stored as a nil pointer, and there is never some allocated memory with a length prefix of 0. When the length reaches 0, the string is always unallocated by the RTL. Note: I usually see people writing if length(something)=0 then and still thinking that it is faster than if something='' then. This is plain wrong. The faster version is the latest: if somestring='' - it just checks if the variable pointer is nil, whereas calling length(), even if it is inlined, generates more assembly, and is slower (dual comparison, and an additional jump if the string is void).

There is a new beta available. Changing the version number to 15 resembles not only the completely different new look due to theme support and new icons, but also the internal changes necessary to make all this work. Hopefully I didn’t break too much.

Interesting reading: http://www.fmxexpress.com/learn-how-to-deploy-delphi-10-3-rio-android-apps-to-google-play-with-android-64-bit-requirements/

A few toolbar issues: 1. The entity insight bar seems to occupy the top toolbar row. It doesn't matter if it's visible or not. See screenshots below. 2. The entity insight bar doesn't have a context menu and can't be customized.

I think your code did not work with Delphi Tokio (10.2.3) either. You should set the stored property of your child components (Panel, Rectangle, Timer) to false.

For me, I found it useful in the following cases: - The Sync mode utility works great with EmptyStr. - I edit a lot of my pas files manually using Notepad, so I just select one EmptyStr and I can clearly see all places where the EmptyStr was implemented. - Last thing, it's a mind trick, I pay much more attention for arguments that use EmptyStr. Blabla(... , EmptyStr); // focus on that call. Blabla(... , ''); // usually I ignore it.

This must be fixed by embt!

@A.M. Hoornweg Well...your users have to cope with it, and you have want to give your users a product, that they can rely on. Win7 is practically dead, so your product has to offer best user experience on Win10 - like it or not.

After I managed to update the license on elc today (thanks again to Matthias Eissing), I was able to compile and use GExperts in Delphi 10.3.2. So far without problems, but that does not mean much because I started and exited the IDE a few times and didn't do much more. I'm busy with other stuff (using Delphi 2007).

At least to my knowledge that is not quite correct. If you are on an active subscription you can contact support for that, if not you need to contact sales. The reactivation is done in both cases. Do you know of any non-subscription user not being able to get a license bump from sales when asking for it? Note: This is just to get the facts right and shall not imply that I am actually supporting this scenario.

For a new migration, I would go into creating a VM. The numbers of Delphi installations is restrained, and after a few setup, you would need to reactivate the licence count - which requires an active licence! So in the future you may need to actually pay a new licence, just to install Delphi on a new computer! (this changed a few weeks ago IIRC) With a VM, you won't face this problem in the future. Also note that creating a VM with Windows 10 is free. You are not even required to validate it, if you can stand up with a black wallpaper - which should be find for a VM running a dev environment.

Can confirm: GetIt is back online!

Is it possible that you have reached the upper size limit for resources? Try removing some other forms and see if the project builds. That would strengthen this hypothesis. I can't begin to understand how you end up with 2000 forms in a single executable.

No, it is not fixed, yet. Permanent solution that will solve all those issues is Delphi LSP (Language Server Protocol) support and is scheduled for 10.4.

Maybe if Andy made 'skins' instead of compiler fixes there would be a free version in it for him 🙂

You can remove the error message by disabling the problematic fix: Tools -> Options -> IDE -> Environment Variables In the "User System Overrides" add a new Variable "IDEFixPack.DisabledPatches" (without the quotes) For the value, enter "CodeGenMod.Win32.FastFuncProlog" (with the quotes) Save and restart the IDE Remember to remove this entry if a new IDEFixpack version is installed 🙂

You can checkout https://github.com/KodeZwerg/versionselector to see how different delphi versions work with registry. All legit stuff from early up to Tokyo 10.2.3 is supported.

Yes, we might have to consider changing the header of this thread to (un)available. 😄 The import part getit.embarcadero.com is still denying access and that is where all the fun is stored.