Leaderboard

OT: BPL hell. I build monolithic applications. copy the exe anywhere and run it. Never even considered using dll or bpl "technology". All I ever see is drawbacks to this kind of software development.

I've installed 11.2 quite a few days ago upgraded from 11.1 (smooth upgrade without problems with web installer). Til now I have only recompiled/updated some of third party libriaries and do a little stuff for a couple of half days on the future release of my main app (in this moment I'm working heavily on the older project still on 10.4.2). Til now I worked without IDE crashes and this is good news for me! On same project on 10.4.2 (but also with 11.0 and 11.1) the IDE crashes all time with various internal errors)! I'll stress the new IDE in the next days but in my way of use it seems definitly more stable.

With Delphi 11.1, my actual output is exactly what you expect.

There are types of applications that benefit a lot from this concept, where I can hardly imagine how it would be without it. Just to name a few I heavily work with: Delphi IDE, RAD Server and FinalBuilder.

gonna give it a try, with a small private project. btw bough the cookbook 😉

DMVCFramework is fully stable and tested. I use DMVCFramework in large production projects, in Windows and Linux environments.

I have learned the hard way that its a bad idea to use XCode beta versions, since they might not match to the iOS versions well and also might show many installation quirks. Thats why I usually wait until at least the finals were ready (also they contain glitches from time to time).

I am using 11.2 and XCode 14 beta 6 and have successfully submitted my program to the app store. Just waiting for review and hopefully it gets accepted. Note: This is on Ventura Beta. Thanks

When Ctrl+click stops working for my projects, I found the best and easiest way to get it to work, I just switch between Release/Debug configuration (and back) and you can see the Codeinsight process does something and Ctrl+click starts working again. So, if I develop in Debug and Ctrl+Click stops working, I double click on Release, wait 1s to see Codeinsight progress shows up, then double click to go back to Debug config: Annoying, but works almost every time and it takes about 5 seconds. So, not too bad.

It's true that the 64 bit Windows debugger is a disaster zone. But I just debug with the 32 bit debugger. You can have a project with both 32 and 64 bit targets. You can then ship just the 64 bit if you prefer. But you can still use the 32 bit debugger during development, because it's the one that is actually useful.