Lars Fosdal

I successfully downloaded it just now, and I did not get a warning. I have to say that I became very skeptical when I saw Softpedia mentioned, as they have a long history with bundling files with other installers like "helpers" for browsers. I did not run the installer.

Wow, you've been lucky. Perhaps it is primarily a plague for corporate developers.

In theory, it is possible to take a .dfm and convert it to an SVG illustration. Not sure there is a huge commercial market, but it surely is something that many would appreciate having to avoid those pointy haired bosses thinking that your two-hour-tossed-together-good-looking Delphi prototype is a complete application that just needs a little testing.

Aha - I assumed the UnixToDateTime did milliseconds - but it also requires seconds. If you change your code to CallTimeDouble := UnixToDateTime(Round(StrToInt64(DATEx)/1000), false); you should get local time, which for you is UTC + 3 ? So '1587377791601' is 2020.04.20 13:16:32,000

program Test; uses SysUtils, DateUtils; const USec: Int64 = 1587377791601; var dt: TDateTime; begin dt := UnixToDateTime(Usec); Writeln(FormatDateTime('yyyy.mm.dd hh:nn:ss,zzz', dt)); end. spits out 52272.01.01 03:26:41,000 Are you sure that you wrote an actual example value?

To write an expert that helps separate the UI from the logic would be far from trivial. I strive to write code that is testable, something that Steve McConnell's "Code Complete" drilled into me. My logic routines and biz objects are created without a UI, and the UI itself is connected afterwards. I make an effort to isolate the displayed data from the data that is actually used. I.e. a grid only reflects the underlying data, and all work is done on the underlying data and not the data in the grid itself. A checkbox state reflects the underlying state, and a change to the checkbox affects the underlying data - which then again applies any recalculations to states, and suggest a refresh of the display. The benefits: It is easy to write unit tests and integration tests for the biz logic. It is easy to reuse the code, or change the UI. It also simplfies changing the biz.logic as it is inside the "black box" object, and not heavily tied to the UI. If the tests says the object works, and the app doesn't work - the error is in the coupling between the non-visual object(s) and the UI. The drawback: There is a certain degree of data duplication - but the cost of that is quite limited. You can use proxy classes and/or Attributes/RTTI to associate elements between the non-visual and UI elements. Divide and conquer is good - but hard unless applied from the start on.

http://docwiki.embarcadero.com/RADStudio/Rio/en/TeeChart

Have you setup the required permissions in the Android manifest? From https://developer.android.com/reference/android/telephony/PhoneStateListener#onCallStateChanged String: call phone number. If application does not have READ_CALL_LOG permission or carrier privileges (see TelephonyManager#hasCarrierPrivileges), an empty string will be passed as an argument.

https://docs.microsoft.com/en-us/windows/win32/perfctrs/using-the-pdh-functions-to-consume-counter-data

Wow! That fact had eluded me!

The book gives a reasonably good understanding of threading issues. That understanding would suggest alternate solutions that avoids the pitfalls of messaging.

A good place to start for writing solid thread code: https://leanpub.com/omnithreadlibrary

Ref installation: You can safely install without elevating to localadmin.

If you had TMS libs from before, like the TMS Component Pack, those are purely VCL for Windows. There are currently two alternatives for cross platform: 1. FireMonkey + TMS FMX Components https://www.tmssoftware.com/site/products.asp?t=fm (All Firemonkey supported platforms) 2. CrossVCL https://www.crossvcl.com/ - not compatible with TMS for VCL, afaik. (MacOS and Linux) Disclaimer: I've not used any of these, only the TMS Component Pack for VCL.

Using the std TJson class in REST.Json. Probably not considered gold std.

Yes. I use the thread class name and an instance id.

Also, monitor your memory consumption in the Windows App. If it is not stable but keeps growing - there is a chance that you have a leak.

That is never wrong. Please ignore me 🖖

Not sure why one would want to do this in a Delphi app, when the tools are right there in PowerShell. https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-hotfix?view=powershell-7

Firefox? I assume Firemonkey. You are more likely to get help if you are specific with regards to what you want to do.

I know... My indendation style is unconventional. It works for me, though.

Scoured our complete source code and found only one occurence each of pred and succ. One was legit. for e := Low(TElementType) to Pred(High(TElementType)) do // i.e. do not include the last enum value in the loop. The other one was a bullshit one - and I was probably the author of both. function AfterFirst(const Match:char; const st:string):String; var index : Word; begin index := pos(Match,st); if index <> 0 then Result := Copy(st, index + 1, succ(Length(st) - index)) else Result := st; end; It's not even consequent.

How about using MadExcept or EurekaLog ?

That said, there is BigInteger from https://github.com/rvelthuis/DelphiBigNumbers

An IPv6 address is 128 bits. The answer is no. You'd need two UInt64s to hold that.