Sherlock

I was tasked with finding a way to know if files have been altered. The possible alterations can only be caused by either system failure or a semi malicious person as the computer is not connected to a network and the gain for said person is...minimal at best. In both cases the altered files would have to be recreated instead of reused which would slow down a different process a bit. In short these are cache files. And of course the best way to know if a file has been altered without permission is a hash, since Windows permissions are sketchy at best. One of these files grows by roughly 2600 Bytes every 5 seconds, and therefore it would be necessary to rehash after each such interval. The system would be generating up to 20 of these files "simultaneously" with each of these files being about 6 hours long on average and may peak at 24 hours. So in Bytes we are talking on average 11MB peaking to 44MB. Here's the question: What would be the best way to do this without to much of an impact on performance. I could use Delphis built-in hashing system.Hash.TSHA1. It is pretty straight forward, but before I dive in on the shallow end of this pool and break my neck...perhaps one of you has a better suggestion.

Done @David Millington https://www.delphipraxis.net/214805-arbeite-fuer-den-embarcadero-vertrieb.html

OK, but my application might crash and then the file might not have been hashed or even written. But I guess I could express the need to perform a "complete reload" after a crash. But it's not nice...

There's an argument I can subscribe to: Spare us the syntactic sugar of the last 15 years and concentrate on the bug fixing. Digit separators, generics, inline variable declaration, multiline string literals, string-like operations support for dynamic arrays? Can them all, and burn the heretics who asked for them

And we cry about the issues because of that almost every day...at least if we are at all concerned with security.

Now there's something the folks over at Embarcadero can aspire to. Imagine built in memory safety in Delphi.

In the past I have encountered some issues with the classic mount scheme, especially in WiFi environments, where a temporarily lost connection could lead to a permanently (until next reboot) lost mount. I have found autofs to be a perfect solution for this and also a good way to reduce network traffic. Here is a small explanation: https://documentation.suse.com/sles/15-SP2/html/SLES-all/cha-autofs.html. And after looking into this I found newer versions of systemd are capable of the same thing, just read here: https://anteru.net/blog/2019/automatic-mounts-using-systemd/.

The certificate is there to show that someone feels responsible for this file. And is confident enough to stick his name to it. Since then it has not been altered.

The future of vmware is uncertain since the Broadcom acquisistion. At least their "larger" products have been switched to a pricier model. At the moment they say that workstation and player remain untouched...for now. https://borncity.com/win/2024/01/19/after-discontinuation-vmware-player-workstation-and-fusion-seems-to-remain/

What protocols does this distant server support? Which authentication steps need to be taken? Can you manually or by other means do this task? As soon as you can answer these questions...you'll get an educated answer.

Your interface definition for example. Not deeper coding knowledge needed for that.

It is quite simple: Only request permissions you really need. Then explaining why you need them is a peace of cake.

This or I would suggest to keep going with dummy spaces and to remove then at runtime. Then, no hints are displayed where none are there to display.

OK, before this discussion gets out of hand. Might I suggest @techdesk to start a project on Github, SourceForge or any other collaboration site, and then present it here? Anyone interested will surely join you.

Please don't drift off to LLM troubleshooting or comparisons. This is a thread for a Delphi 13 wishlist.

This is solved, as soon as Embarcadero has solved their server issues. Read here for more informations

Bug fixes, bug fixes and after that: more bug fixes. Don't release until there are no more unresolved bug reports. Quit following hypes just for the hypes sake.

Well since MDI forms have experienced a major redo for D12, I would suggest looking there.

Considering the 1337 attitude of some developers ("well written code is self explanatory") they might just have the best Delphi coders in the world... however, seeing as the RTL and VCL are very often a source of inspiration and for learning, I would also appreciate more well written comments. Perhaps not line for line, but at least stating the intent of the following code block or the reasoning why this way was chosen over another.

This is always a very good idea, unless you are trying to develop something like hardware drivers.

It has always been my understanding that you may continue to use the product after the license expires, you just wont get updates or assistance. But that cited text there reads quite troubling. You should be aware though, that there are different license agreements for different countries. So please make sure you are reading the correct one, concerning you and where you bought the license.

Well, it looks like the FMX.TListView might be able to do the trick...not VCL, mind you! For VCL follow @PeterBelow

1. May I suggest to quickly edit the first question and translate the title to english 😉 2. The version in question is quite surely XE7 which for some people is also "just" 7.

Those are just TButtons with three dots in 'em. It is up to the programmer to react to the OnClick event and open up whatever dialog is desired.

Fixed the title. Should the fix be wrong, or if it can be improved. Just holler.