Lars Fosdal

I just tested. In case you forgot to backup your \Program Files (x86)\Common Files\ParnassusShared folder, you can uninstall/reinstall Navigator for 11.x without affecting 12.x. Not sure of how that would affect 10.x, though.

Navigator causes a number of issues. I recommend uninstalling it for 12.0 if you have it installed, before installing 12.1. And, yes, it definitively screws the 11.x install as well, so back up the old DLLs before uninstalling and reinstalling

Variable not initialized - I set that one to raise a compile error - because those WILL bite you. Also, you will get that if you init the variable inside a try block, instead of before the block. Hints are often nearly as important as warnings. Value never used can f.x. mean that you are referring to the wrong variable elsewhere you are mistakenly replacing the value elsewhere before the one you initially set could be used or, you didn't need to set that value because it would have been set elsewhere anyways

I've not had issues with this as long as I keep the old settings. I upgrade two VMs and my workstation. If you run into installation counter issues, contact EMBT support. As for GetIt installations - yeah... that is "fun". I keep my IDE on a GetIt component low count diet.

@shineworld AFAIK, only patches and hotfixes come via GetIt. @Tommi Prami Yes, the installer barfs on restarting the installation due to Navigator, but it should be able to recover. Mine did.

https://blogs.embarcadero.com/announcing-the-availability-of-rad-studio-12-1-athens/ https://docwiki.embarcadero.com/RADStudio/Athens/en/12_Athens_-_Release_1

It downloads as 7.2Gb.

That is indeed a bit odd, since the 12.0 ISO was 7.13Gb.

There are ways to do that - but none of them are easy or backwards compatible.

Took me a while to get past all the Ios island travel tips before finding this: https://developer.apple.com/design/human-interface-guidelines/live-activities Not sure if supported in Delphi?

IDE and Compiler: Pretty hard! That would not be a recompile. VCL and RTL: Should be possible to port, assuming the Windows APIs are mostly "the same" for ARM as for x64.

If the form designer of Delphi could be called out-of-process, it could be paired with VSCode, and personally, I really like VSCode. Then again, the shortcuts in the BDS IDE are engrained in my muscle memory...

Are you looking for a mechanism that is general, and can be applied to many queries? What is the expected lifecycle for the DataObject, use as discardable parameter only, or extend with more properties and methods and store in other data structures? I assume you want type safety so that an int/float/date/string in the db is represented as an int/float/date/string in the DataObject? The obvious choice is to create a custom class tailored to the query. Upside is performance and custom adaptation. Downside is that you need to implement a new class and handcraft the conversion for every query. A more flexible, but less performant approach, would be to use RTTI to map DB Fields to DataObject properties. either into a class or into a record type. Basically, you would use RTTI to examine the property in the DataObject and use the name to look it up in the query, and the type to make the appropriate copying. However, the distinct needs you have would have to be explained in more detail before we could detail the appropriate solution.

My workmachine is not quite JRE free, due to IBM ACE. But in general, I don't install Java apps if I can avoid it.

Fun observations on the GoTo topic: https://jerf.org/iri/post/2024/goto/

If there is a new version or patch for the IDE, it also will show up on the Welcome page.

Frequent scenario function Test: integer; var i: integer; begin try i := 1; // do something finally; Result := i; end; end; i needs to be initialized before the try block.

Peganza is another possible tool to find out which unit that drags in another unit.

@riev96 cglm.ini file will not help you. There is no license info in that file. SLIP files, on the other hand, are personal, and not to be shared.

Personally, I shun LiveBindings. In my experience, they are slow and fragile. Disclaimer: I haven't tried them since the version of Delphi when they first arrived.

I've never tried working with subforms, so I can't say much about that.

Another benefit is that we usually wait with initializing the frames until they are actually used. Saves init time on app startup.

We use a lot of frames, but we almost always instantiate, reparent and connect them at runtime. Usually, we have a panel as a "host" for the frame, which lets the panel deal with the in-form alignment, so that the frame can use alClient. As @Davide Angeli mentions, loss of events has been a key factor for deciding to do it that way.

MS Copilot might be able, but, yeah, elbow grease FTW.

That feels almost like you're advocating the use of FreeAndNil 😄