DelphiUdIT

For something to be patentable it must have a creative and innovative character. I don't think that a few lines of assembler can be considered as such.

Catch the clipboard is really simply, why don't you do it ? Using the JvClipboardMonitor, you can "ear" all "copy" actions, you can also choose what you are cacthing (look at source of JvClipboardMonitor and Microsoft docs). That example is simple, no control about the "paste". That catch also the administrator level "copy" and all copy / paste password .... like @Brandon Staggs said. unit Unit1; interface uses Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, Vcl.Graphics, Vcl.Controls, Vcl.Forms, Vcl.Dialogs, JvComponentBase, JvClipboardMonitor, Vcl.StdCtrls; type TForm1 = class(TForm) JvClipboardMonitor1: TJvClipboardMonitor; Memo1: TMemo; procedure JvClipboardMonitor1Change(Sender: TObject); private { Private declarations } public { Public declarations } end; var Form1: TForm1; implementation {$R *.dfm} procedure TForm1.JvClipboardMonitor1Change(Sender: TObject); begin Memo1.PasteFromClipboard; Memo1.Lines.Add(#10#13); end; end.

I update this topic 'cause new versions are released of Halcon (and quote Matthias that were interested about that). I post a Delphi wrapper around this, not a really Delphi wrapper, only a porting from C headers that I have done with CHET. Take care that some adjustments should be done from your previous sources because in Halcon are changed some records (Tuples), and for other reasons too. Read carefully the "Release Notes for HALCON 24.11.1.0 Progress-Steady" (https://www.mvtec.com/products/halcon/work-with-halcon/documentation/release-notes-2411-1) for full details. I tried the new wrapper only partially. Bye HalconC_2411.pas

The indication on the "GOTO" page is not precise, it was always like this.

Something wrong with your update, the build should be "29.0.53982.0329" ...

A digital signature remains valid until it or the issuing certificate (chain trust) is revoked. When it expires in time, it is still considered valid. You cannot use a certificateto for signing purpose that has already expired, obviously. As for OSCP and CRL, in any case the possibility of invalidating a signature (or a certificate) must be guaranteed ... it is the basis of the concept of public signature. I don't know for how long it will still be possible to use "file" certificates like those of LET'S Encrypt for uses other than simple SSL ... the legislation (for example the Italian one) considers the digital signature valid ONLY and EXCLUSIVELY if produced by HARDWARE devices (specific), and it seems to me that the rest of the world follows this. So certificates with a validity of less than 1 year are not feasible if combined with classic USB TOKENS for example. Bye

A public signature is subject to revocation, which I can imagine would happen very quickly if a malware signature is verified. Also, the signature would be easily identifiable and the malware could therefore be blocked in virtually "zero time".

And all the features about 12.2 Release. The CE edition is like the 12.1.

Here will be all features for the various RAD Studio Editions (included CE): https://www.embarcadero.com/docs/rad-studio-feature-matrix.pdf

If you refer to this notice of CVE: https://github.com/madler/zlib/issues/868 they have resolved with 1.3.1 version. And the new Delphi version use the right version:

Sorry, but you are not right. For example no one can ACQUIRE data about HEALT status without your explicity WRITTEN and PREVIOUS consent. Thw European law is not only about how you threat the data, but also about you acquire the data ... So if one send you a screen shoot with name, age a healt status behind the scenes, you will be in fault if you don't have the explicity consent. This happened to a client of mine (for whom I made a piece of management software). It is not uncommon to find difficulties in sending information, that is, sending it and having a response, due to the GDPR.

I dont' know these components, but the error (you show incomplete message) seems to indicate that the scanner driver is not installed (or the scanner is offline). Again, I do not know the components nor have I ever developed a scanner application, and I could certainly be wrong.

I really don't know what to say ... I have no issues about this, and I debug to asm level too. But I really don't have any issues on debugging. And I'm using the offline installer too (I've always used it). Good luck.

You don't have the UPDATE version of RTL (I mean 12.0, 12.1, 12.2) with VERxxx. By now if you see a lot of packages like Indy, FastReport, Jvcl, etc ... they use near they same like you example, but there is not minor version (UPDATE) identity: you can see Delphi12 but not Delphi 12.2, all minor releases are indentified like Delphi12.

I explain BAD: the example I suggest is like @limelect do with JVCL -> VERSION IS FROM APP INFO, NOT FROM DELPHI VERSION. FOR Delphi version, like I told more times there is the "GetRTLVersion" function from System uniti: https://docwiki.embarcadero.com/Libraries/Athens/en/System.GetRTLVersion

It come from INFO from application setting. You can use also in this way (I use it since decades without JVCL) ( EDIT :THIS EXAMPLE REPORT INFO FROM APP INFO, NOT FROM DELPHI VERSION !!!) function GetAppVersion: string; var Size, Size2: DWord; Pt, Pt2: Pointer; begin Size := GetFileVersionInfoSize(PChar (ParamStr (0)), Size2); if Size > 0 then begin GetMem (Pt, Size); try GetFileVersionInfo (PChar (ParamStr (0)), 0, Size, Pt); VerQueryValue (Pt, '\', Pt2, Size2); with TVSFixedFileInfo (Pt2^) do begin Result:= 'Version: '+ IntToStr (HiWord (dwFileVersionMS)) + '.' + IntToStr (LoWord (dwFileVersionMS)) + '.' + IntToStr (HiWord (dwFileVersionLS)) + '.' + IntToStr (LoWord (dwFileVersionLS)); end; finally FreeMem (Pt); end; end else begin Result:= 'Version: NOT RECOGNIZED'; end; end; I think he wants to have the version of RAD STUDIO that build the exe file. The GetRTLVersion do this (to UPDATE level) and it is include in the System Unit.

Yes, you can use the GetRTLVersion function. That return the Major release and Minor release ... for example Athens12.2 -> is $2402 Only Update level version, no patch informations. It is a new function that works from Athens 12.

I think that file is part of commercial project, you must pay for it: https://www.eztwain.com/

I remeber somethings about decades ago ... may be the property is Sheet.Cells[x, y] or Sheets.Cells[x].Column ? For your facility, if you import the Excel typelib, you will able to see all properties of all "components" in the "Excel..._tlb.pas" created. These should be near the same as you use with OleObj.

I disagree the use of pointers directly for a waste use. In the past I had some side effects not "beauty" ... especially if they were targeting structures with "managed types". In the state of Darian exposition, I will prefer the mix solution. CodGen projects are always "beasts", I wish you good luck in your job @Darian Miller

In GetIt online page this is appeared: It's a new build, this means that a patch will be released soon ?

NO, also Delphi and some more then this ( like NDK ?). EDIT: No NDK update. The patch is installed in 10 seconds without any Issues.

I agree with you, and in the past i reported in QP that. But sometimes I fill (always in the past) that some Issues found on IDE were about some components. But that was only a perception I was not sure about that, and replicate this was difficult. So, I tried in this way. Now, really I dont'use IDE comp. from thirdy-parts that need to be used in designer. Some exceptions are from JVCL (very few now) that never give me any trouble or some other historical little tools (for example I have the TSPVoice installed in the palette, but I never used in the designer ). Also some visual tools about artificial vision (where I can simply make a component for designer) are used to be construct at runtime (construct some dozen of windows over one or two TPanels). The RAD, like you told, should be the best way to construct an application, but this doesn't means that ALL should be done in the designer. And for me that work a lot with threads, the "runtime way" for many "components" are the best way.

I, and not only me, have noticed that the instability of the IDE is mainly due to (in my case ONLY to) third-party components installed in the IDE. For a long time now I have been trying to use third-party components (there are few that I install now) only at runtime. And where a graphical surface defined in the FORM is needed, I "hook" them to invisible TPanels placed at design time. Of course, not always it's possible but when it is that save me about those issues probably.

The "Adopt" is there, empty from the previous version ... I don't use Adopt, I use Oracle JDK 22. Of course, I agree ... and may be that if someone knows the answer ... is under NDA. But I've never seen different versions of the NDK than the IDE build. I probably never paid attention to that.