Leaderboard

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.

Embarcadero http server is probably installed on Marco smartphone, and sometimes it happens that Marco is out of reach of the network 😉

We have noticed that Documentation Insight was broken in the latest Delphi 10.3.2 update. Here is the hotfix: http://www.devjetsoftware.com/downloads Thanks for your support!

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 🙂

Thomas, Unfortunately, it would seem something has changed in RAD Studio which is now crashing GExperts. The following appear when you shutdown the IDE (whether its immediately after opening or after a time of working). I know its GExperts as I've removed all experts and added them back one at a time until the last one to be added was GExperts (as I suspected it might be - only because its likely to be one of the few experts that will work outside of the OTA). I've tried to get more information by changing EurekaLog's IDE settings to capture all errors but it would seem they are happening after the EL BPL had unloaded. If you need more information, please ask and I'll debug the IDE with the IDE (although I don't have the GExperts source).

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

Are you using 3rd party C libraries in your Mac app? Or maybe some custom assembly code? Then things will be different when you switch to 64-bit macOS. Maybe this post will give you a head start. It shows how you can use static libraries now, and how you can use an external assembler for your assembly code. https://blog.grijjy.com/2019/07/19/using-static-libraries-and-assembly-with-64-bit-macos/

I've just updated SVN and the overnight zip so that ICS will build properly again, tested against Delphi Rio 10.3 Update 2, aka 10.3.2, no changes were needed. There are some minor fixes from this forum, with a lot of other pending units waiting mostly relating to automatic ordering of Let's Encrypt SSL certificates, just got to fix one SSL bug in socket server. Angus

The change to report exceptions rather than hide them is now in SVN. Angus

Which brings us back to another conversation... I will not comment on

Hi All, Thank you all for your pointers and consideration. I have now amassed the following routines which I think will get me there with some massaging. ExecuteAndWait. TerminateProcessByID. GetPIDByProgramName. ExecuteProcess. I will let you know how I go, or not. ;-) Regards & Tks again, Ian

Indeed. I just always like to read MS documentation first. So those would be my first steps. After I collect all necessary API calls, I would search Delphi RTL/VCL source to see if anything is already implemented somewhere... and yes, then Google again for specific Delphi implementation if needed (I can generally manage using Windows API calls without additional searching, but that knowledge depends on how often one has to interact with Windows API directly - Delphi does good job at hiding and wrapping those parts so many developers don't have the need to do low level interactions)

@Dalija Prasnikar I would always add Delphi to the search query. But other than that, Ian should now be good to go.

http://altd.embarcadero.com/download/radstudio/10.3/radstudio10_3_2_esd_496593.exe

Version with b is newer. quality.embarcadero,com and cc.embarcadero.com are down...

Hi David, "Easy" Says he who knows how to do it. ;-) I have no idea how to do what you described. Ian

More accurately, it just says that the NIST ITS's usage of the TIME protocol is obsolete and NTP is preferred, not that the TIME protocol itself is obsolete. This page explains it a bit better: https://www.nist.gov/pml/time-and-frequency-division/services/internet-time-service-its Yes.

It usually takes some days to mark them as closed after they release a new version. This is because they have two different servers one for internal issues and one for public issues.

Unified memory management only affects mobile compilers and if you are developing for Android you will have to use 10.4. Developers developing for iOS will still be able to use 10.3.2 for a while, but probably not for too long... and even for them it would be smart to switch to 10.4 as soon as possible to adjust their codebases. As far as LSP is concerned... code completion and navigation as well as code insight is pretty much broken as-is... I cannot imagine LSP in its first release being so bad that it would justify staying at 10.3.2. Also 10.3.2 and 10.4 can live side by side... so you can have both and use version that is more appropriate for any particular reason you may have.

Only saw examples at online to select one file in explorer, and thought maybe someone else can also benefit from version that selects multiple files. Or harden this one if needed, -Tee- function OpenFolderAndSelectFiles(const AFileNames: TStringList): Boolean; procedure CheckFilesHaveSameRoot(const AFileNames: TStringList); var I: Integer; LDirectory: string; begin LDirectory := ExtractFilePath(AFileNames[0]); for I := 1 to AFileNames.Count - 1 do if not SameText(LDirectory, ExtractFilePath(AFileNames[I])) then raise EFileNotFoundException.CreateFmt('File "%s" is not in common root "%s"', [AFileNames[I], LDirectory]); end; var LDirectory: string; LPDirectoryItemID: PItemIDList; I: Integer; LFileArray: TArray<PItemIDList>; LDidInitCOM: Boolean; LAPIResult: HResult; begin CheckFilesHaveSameRoot(AFileNames); Result := False; LDidInitCOM := False; LDirectory := ExtractFilePath(AFileNames[0]); LPDirectoryItemID := ILCreateFromPath(PChar(LDirectory)); if Assigned(LPDirectoryItemID) then try SetLength(LFileArray, AFileNames.Count); for I := 0 to AFileNames.Count - 1 do LFileArray[I] := ILCreateFromPath(PChar(AFileNames[I])); while True do begin LAPIResult := SHOpenFolderAndSelectItems(LPDirectoryItemID, AFileNames.Count, @LFileArray[0], 0); if LAPIResult = CO_E_NOTINITIALIZED then begin LDidInitCOM := Succeeded(CoInitialize(nil)); if not LDidInitCOM then raise Exception.Create('Could not initialize COM'); end else Break; end; Result := LAPIResult = S_OK; finally ILFree(LPDirectoryItemID); for I := 1 to AFileNames.Count - 1 do ILFree(LFileArray[I]); if LDidInitCOM then CoUninitialize; end; end;

Can't argue that... Problem is that expansion to other platforms started as customers request. If we all knew then what we know now, maybe things would play out differently.... on the other hand, maybe not... when you have need to support other platforms and your toolset does not have them, you have to find some that does... when you start moving away, sometimes you may be inclined to move away completely. Also, development team shrinking process happened after expansion to other platforms... Quite unexpectedly, if I may say, because at that point it should have been obvious that more platforms means more work and more work requires more people, not less. We can argue here until the end of the world, but how can you argue anything when actual events (decisions) defy all logic. For all we know, maybe even without additional platforms Windows side would be in similar position as it is now.

Unfortunately there' ll be no futher versions.

And run against the registration count wall and have to whimper for a bump?

Yes, I can not install CE version too: