TurboMagic

Thanks for the info! That one works for me. My DNS is an inernal one so Google etc. don't help me...

Ok, I can query this TXT record now, when I know the IP of one of our internal DNS servers. But how to find that one out? Yes, cmd.exe -> ipconfig /all would tell me, but I need to implement this internally. I tried to understand what THTTPCli does to determine that, but I failed to do so. Is there some other easier solution available to get such an IP-address? I know that I can have several connections and thus several DNS servers. but I think I can manage when I get a list of all those.

Well, I won't use this for e-mail, but the data will most likely not change often, if at all. But this is good to know for first tests.

Ah! Yes, you're right! D2009 was Generics and Anonymous methods...

Thanks, this looks like what I'm after.

Ok, time to upgrade. I see. Thanks! What I learned is, that TXT records can have a name and thus I could retrieve that one with this?

As far as I remember Win64 compiler was introduced with D2009 already.

Hello, I've got some good news and sort of a Christmas present: What is it? Delphi Code Coverage Wizard V2.0. A GUI to make using the CodeCoverage.exe tool easier. Oh and what please is code coverage? With code coverage one can find out whether the unit tests one has (I do hope you have some!) really cover all of your code or if you missed some scenarious. If you still are unsure how that looks like you might have a look at the screenshots provided at the bottom of the project's github page here: https://github.com/MHumm/delphi-code...ge-wizard-plus Now where to get this fine tool? https://github.com/MHumm/delphi-code...eases/tag/V2.0 Hopefully via GetIt package manager soon as well. That one currently still contains V1.1 A list of the improvements made between V1.1 and V2.0 is found on the release URL above. Now enjoy it TurboMagic

Well, I'd be gratefull if somebody could grab that new version from development branch and test the new additions to find out if I understood and implemented those correctly.

This one only exists since 10.4 or 11.x or so...

The issue is: CE is such a system. You are only allowed up to a certain $$$$ you make a year. But EMBT isn't MS which has more revenue streams and thus can better stay profitable even if a number of persons misuse the free version as replacement for the paid one. That's also the reason why CE only is being released months after a new major release.

Well, paying subscription users usually get an invitation to the beta as well nowadays afaik.

Not sure where you looked at, but for Delphi Android and iOS are supported. For Android the SDK 33 requirement is fullfilled with 12.0 now. If you should be a C++ Builder developer things would look differently, but since this is a Delphi forum I doubt you are one... 😉

I also struggle to load a .so. In my case the .so was created in Delphi for testing purposes. I tried to follow your idea with the deployment but I didn't fully understand this yet. Is this only relevant if I'm building an .aab later on? I'm currently still struggeling with a normal apk / debugger / debug build. I'm currently using an Android 11 device but will test on a Android 13 device in a few minutes. On the device used the first call to SafeLoadLibrary results in a Segmentation fault(11) crash. Here's my code: procedure Tf_Main.b_CalcClick(Sender: TObject); var Handle : HMODULE; s : string; begin Memo1.Lines.Clear; s := TPath.Combine(TPath.GetLibraryPath, 'libSO_Test.so'); if System.SysUtils.FileExists(s) then Memo1.Lines.Add('Exists'); Handle := SafeLoadLibrary('libSO_Test.so'); Memo1.Lines.Add('Handle1: ' + Handle.ToString); if (Handle = 0) then Handle := SafeLoadLibrary(s); Memo1.Lines.Add('Handle2: ' + Handle.ToString); if (Handle <> 0) then begin try FDoAdd := GetProcAddress(Handle, PChar('DoAdd')); if (@FDoAdd = nil) then Memo1.Lines.Add('Failure loading proc (is nil)') else begin l_Result.Text := FDoAdd(tf_Summand1.Text.ToInteger, tf_Summand2.Text.ToInteger).ToString; FDoAdd := nil; Memo1.Lines.Add('Success'); end; finally FreeLibrary(Handle); end; end else Memo1.Lines.Add('SO handle is invalid'); end; Any idea?

Hello, the DEC (Delphi Encryption Compendium) library recently got a pull request from somebody to make it more compatible with FPC. While that's nice I took that request, but found out later, that it made it no longer compile on Delphi. With some help of Stevie I got that fixed, but I guess it now doesn't compile on FPC anymore. The issue is the use of IFDEF/IFEND etc. constructs. While I want to stay FPC compatible with DEC I have not enough knowledge of FPC and I also lack the time to look after that part right now. So I'd be grateful if somebody could look at this and make suggestions how to change it so that it is compatible with both. Cheers TurboMagic

This is the information that I added a few things in development branch of this tool lately. I updated the command line code coverage tool used and started to add the new parametrs it provides. I haven't yet added all and I don't think all make sense for this tool, but you might still want to try it out. I haven't tested those additions yet, as I don't fully understand yet how they must be used from that bit of documentation provided for them and now I have lack of time, but I still hope they're usefull as is. So if I get feedback on them (and I didn't completely missunderstand those) I might still get a new release together soon. Cheers TurboMagic

I'm using FastReports Embarcadero edition. I'm looking for an even which signals me, that the report has been output (saved as PDF or sent to the printer). I haven't really found a suitable event yet. Maybe I just overlooked it?

I'll try to find the time to look into those examples tomorrow. I have to find the cause of some memory issue where my report generating class gets an interface reference, which it stores as a field in the object instance. It takes some of the data from it and assigns that to the report components in OnGetValue event. But when that event is called, the field with the interface reference is NIL! I haven't found out yet, who nils that reference or who overwrites that memory... 😞

I wrote the OnAfterPrint events into some log now and it looks now, that this is not called after printing the complete report, but after printing each "component" on it. Reading the manual I find this confirmed: it is called after each band at least. I was looking for something being called after the complete report has been output.

The event would be used to clear some data once the output has been created and thus Fast Reports no longer needs to have access to that data. Since the output is mandatory that shouldn't be problematic.

Thanks, will try this one! In those cases where I print/output without preview the user cannot cancel 😉

Hello, this is to let you know that there was a open source collaboration project started to create a formal specification of the Delphi language in Backus-Naur format (https://en.wikipedia.org/wiki/Backus–Naur_form). It is hosted on GitHub here: https://github.com/MHumm/DelphiGrammar David Hoyle contributed his Delphi 10.3 version as a starting point. If you want to participate in this endeavor, which might help developers of language tools, just drop me a message with your GitHub account name and I'll give you commit permission. Either via this forum or as an issue on that GitHub project. Currently I picked Apache 2.0 as license, but if necessary we can discuss to use something else. Cheers TurboMagic

Now you discussed this at length but it looks like no clear conclusion was reached yet and nobody seems to have done anything about this grammar. Looks like a grammar is not usefull at all... 😉

Hello, yesterday I released V3.1 of TComPortDrv, a RS232 handling component for Delphi. It is available here: https://github.com/MHumm/ComPortDriver/releases/tag/V3.1 And most likely via GetIt as well. There it's still V3.0, but I already sent in V3.1 to update the entry. What's new? fixed the wrong handle type used, which made it fail in 64 bit applications => it's 64 bit compatible now fixed a deadlock situation which could happen if somebody called MessageDlg from an eventhandler. That called that event handler again which called MessageDlg again which... 😉 So enjoy it TurboMagic

Next useful info: it is available via GetIt now as well!