Leaderboard

ok, but it's not about VCL, it's about projects using C++ and Delphi code

To be fair, they are being very straightforward about it being a "version 1" release and it isn't even enabled by default.

Links to Web installer and ISO are available in https://my.embarcadero.com

It appears that Embarcadero did not include this issue in the known issues listed in the release notes, so I decided to share this workaround. Some users may encounter a stack overflow error when just create a empty VCL application the Delphi 12.3 64-bit IDE on ARM platforms. One of the Embarcadero team members provided a workaround: change the emulation settings to force single-core operation. Although this will slow down the IDE, it should function properly. Let's hope a hotfix is released soon.

It is located in the bin64 subfolder, which already exists. Most of the new 64-bit files are placed there, too. A couple of 64-bit design time BPL and DCP files are added to the appropriate places. The amount of additional needed disk scape can be neglected. The 64-bit IDE shares most of the registry entries, while adding a couple of x64 keys like Known IDE Packages x64 and Known Packages x64.

The 64 bits IDE is optional, you don't have to install it if you don't want to use it. All files are in the standard BDS folder but the 64 bit IDE and files are under a ./bin64 folder. For the registry some parameters are common (like default project folder), some of them are separated (like DCUs paths). More infos about the 64 bits IDE are on https://docwiki.embarcadero.com/RADStudio/en/64-bit_IDE

I like your "just". 😉 The IDE is not the only thing in 64 bits : at least the compilers, debuggers and LSP server. 🙂 That said, I'm using the 12.3 RTM since a week and no big problem appeared. It's a little speeder than the 12.2 on the same VM (Windows ARM on a Mac mini M1). LSP is working well but I don't have worked on big projects.

Prepare for three years of them fixing the new 64 bit IDE

The 32 and 64 bits IDE don't share components packages. DevExpress (and other components vendors) have to add the 64 bits version of them in their installers.

Well, I've just come up with a solution. My problem was that I hadn't noticed there's Large and AccessibilityLarge to contend with. Using units from Kastri (thank you again!) I've cobbled together something that seems to work. I don't know if there is official conversion to a scale, but I worked it out by taking screenshots and then resizing the images to work out the percentages. Hope others find this useful. (Again, if there's a more obvious solution, please comment!) roughtextsizetoscaleconverter.txt

Version 1.1.0.B32 is ready for D11 and D12.3 64 Bit IDE

I only skimmed through the changelog, but what interests me most is the introduction of an entirely new debugger for Win64: https://docwiki.embarcadero.com/RADStudio/Athens/en/64-bit_IDE#Delphi_Debugger That -could- mean a huge step forward in writing & debugging Delphi code outside of the RAD Studio IDE.

I have a similar problem with the GExperts hotkeys. There is a bug report on SourceForge that also suggests a cause and fix for this. Unfortunately I was unable to get it to work.

Because those are the only 2 extensions that the VCL registers for TWICImage. But the WIC library supports so much more. Windows Imaging Component Native WIC Codecs Most likely, yes. WIC can be extended with custom codecs. The VCL does not provide a way to enumerate file extensions that WIC supports. But WIC itself does via its IWICImagingFactory interface, which you can access by the TWICImage::ImagingFactory property. Use IWICImagingFactory::CreateComponentEnumerator() to enumerate its available codecs, query each one for IWICBitmapCodecInfo, and then use IWICBitmapCodecInfo::GetFileExtensions().

After wiping my MAC and reinstalling everything again with no luck, I ended up creating a test app in xcode using the certificates and then everything started working and I could then deploy my app to my iOS 18 device. The test project must have put everything in the right place required by the PAserver. On the bright side of life I now have an extremely clean MAC. 🙂

Used it for a few minutes and sigh bugs we've been waiting for years for fixes still there. Top toolbar drawing problems, already had an av plus freezes and unusable functionality (eg context menu Find Declaration, Find, Find Symbols, Refactor) 64bit IDE won't debug the first 64bit project of ours that I tried. Was hoping things would improve, luckily VSCode is more productive and usable with our code bases, unfortunately still need to use IDE for forms editing and for debugging as haven't got lldb debugging of Delphi code working yet.

I have a good installation. You do not need administrator privileges to work in RAD Studio only to work with GetIt. Also, you need admin privileges to finish the installation. Only when the IDE is started with admin privileges you get the form to select the Dark/Light and font.

The mobile apps I've compiled are working as expected. Waiting a few days is a good idea. If you work with a VM you can clone it and upgrade Delphi on one of them.

ICS V9.4 is ready for RAD Studio 12 Update 3, aka RAD Studio 12.3, and specifically the new 64-bit IDE. The ICS Delphi V9.4 design packages already have Windows 64-bit as a target, allowing them to be installed into the 64-bit IDE. The 32-bit IDE allows design packages to be built with target Windows 64-bit, but not installed. Note the 64-bit IDE does not support Windows 32-bit targets, only Windows 64-bit. If you use the IcsInstallVclFmx.groupproj Build Group, all design packages will be built for Windows 64-bit. All the main samples build OK in the 64-bit IDE, with a Windows 64-bit target being automatically added, unfortunately even when deliberately missing such as the OverbyteIcsNetMon sample that does work in Windows 64-bit. Currently, GetIt only works in read-only mode in the 64-bit IDE, so you will need to install ICS using GetIt from the 32-bit IDE, then start the 64-bit IDE and manually install the three design packages. The ICS V9.4 C++ Builder packages can be currently be installed successfully into C++ Builder 12.3 32-bit IDE for the Windows 32-bit target only. The 32-bit IDE should be able to build for Windows 64-bit and Win64x (Modern) as well, all the package paths are correct, but both targets currently give compiler errors. The C++ Windows 64-bit errors are four unresolved external, and the same error happens in Delphi 11, so should be fixable by someone with C++ knowledge. Building for Win64x (Modern) gives lots of undefined symbol errors due to RAD Studio being unable to import other packages compiled built with C++ Win64x, this error was reported six months ago for C++ 12.2 but is not fixed in 12.3. So ICS can not be used in the C++ 64-bit IDE that only supports Win64x (Modern), not Windows 64-bit. Separately, there is a new version of the DD Service Application Framework used by two of the ICS samples, adding support for 64-bit IDE Wizards. Available shortly from https://www.magsys.co.uk/delphi/ddservice.asp Angus

@CyberPeter Tip: When you enable Skia in your project (right-click on the project > Enable Skia), the next time you build the project, the sk4d.dll will be in the output folder along with your .exe.

You need the Skia.dll file with projects using Skia. Check "Project / Deployment wizard" option to see where it's located on your development computer. It should be in the "bin" folder of RAD Studio installation. See https://docwiki.embarcadero.com/RADStudio/en/Skia4Delphi for other links and infos about using Skia in Delphi or C++Builder.

At program startup, detect the presence of the debugger (dynamically, or via a command-line parameter) and then use SetStdHandle() to replace STDIN with your own handle to a named pipe or anonymous pipe, and then write your desired debug data to that pipe. Or better, simply move your logic into a function that takes an input TStream as a parameter, and then decide whether you want to use a THandleStream for STDIN or a TStringStream or TMemoryStream for your debug data. On a side note - using a 'while (Position < Size)' loop is not a good idea. You should simply call Read() with a fixed-sized buffer, and let it tell you when it reaches the end of the stream, eg. SetLength(Buffer, SomeSize); repeat BytesRead := StdInStream.Read(Buffer, SomeSize); if BytesRead < 1 then Break; // do stuff until False;

Are you sure? List of publicly reported bugs fixed in 12.2 List of publicly reported bugs fixed in 12.1 List of publicly reported bugs fixed in 12.0 List of publicly reported bugs fixed in 11.3 List of publicly reported bugs fixed in 11.2 List of publicly reported bugs fixed in 11.1 List of publicly reported bugs fixed in 11.0 List of publicly reported bugs fixed in 10.4

It works brilliantly, even better than I thought! 😉 When I finish my project, I'll include your name in the credits.

There's some instructions for adding Swift support, here. You will also need to ensure you have the Linker Options configured correctly in Project Options as per these instructions.