FPiette

Any thread/process may create the file but must be prepared to handle "file already exists" error if another thread/process is creating the file one microsecond before. In that context, file already exists is not an error! Then every thread/process lock the file BEFORE writing or reading anything and unlock right after. Now the question is where to lock. File locking allow to lock one or more bytes, and even lock a non existent part of the file. There are several possibilities. The most important is that every thread/process must follow the same rule. 1) Lock the whole file and way past the end of file. 2) Lock a single bytes or a few bytes, usually the the file header, if any. 3) Lock from the byte at end of file for a large block. 4) Lock a single byte far away from end of file, at a fixed place that will never be reached. 5) Another file, maybe empty, is used to place the locks. Solution 1 is easy and the file is completely locked for everything except the one that placed the lock. This include any editor or even the "type" or "copy" commands of the command interpreter. This may be desirable... or not. Solution 2 is frequently used by database manager. Solution 3 will allow reading from a thread/process for the existing part of the file while another is appending to the file. Solution 4 is interesting in some cases because any reader/writer will be able to read/write to the file as usual but all aware of the locking will correctly write to the file without overwriting anything. This may be desirable... or not. Solution 5 is interesting because the file is never locked by thread/process aware of the locking scheme will safely read/write the file. There are probably other locking schemes. The developer has to carefully think about his intent and use case. And of course must fully understand how locking files works. The file locking is the base of multi user applications and exists almost since the beginning of computer software and databases. There are a lot of articles and books published on the subject.

I use LockFile or LockFileEx from Windows API.

Maybe you should write a program to filter Windows event log files which contains all the events you mentioned. Or maybe there is something you don't tell us...

Maybe look at http://www.DelphiFFmpeg.com

Maybe you could consider using "packed record"?

A friend ask me how to register to the forum. I check and see no link to do that! Could you tell me how to register?

What is done exactly?

Sure it is the same ! Nevertheless, uninstall that version completely and reinstall Delphi 12 personality only.

Avec plaisir.

It is likely a path issue. There are DirectX units in DSPACK which are also in Delphi. Your GDIAPI was probably compiled using Delphi's units while your application is compiled with DSPACK. I suggest you get rid of DSPACK. It is an old thing that is no more maintained. I used it in the past and updated my code to use DirectX units of Delphi.

Just look at the GetEvent declaration and the declarations of you variables. BTW: Do you know that DirectX API exists now in Delphi. It was missing when DSPACK was created but now it exists.

Is it what you are looking for: https://github.com/YepSfx/DSPack

When installing retail Delphi 12, the installer should have removed the beta version. Try running the installer again and select remove product (or similar item). Then reboot your computer. Then run the installer to install only Delphi.

Run Delphi personality only: add "-d Delphi" to the shortcut you use to launch the IDE. See the documentation: IDE Command Line Switches and Options

Maybe you are doing computation in the OnPaint event. Decouple computation from presentation (the drawing). For the drawing itself, avoid drawing pixel by pixel on screen. Avoid having hundreds of components to draw. Avoid drawing invisible parts. Painting in a bitmap and then blasting the bitmap on screen could be faster than painting on screen directly.

Use Process Monitor to spy on which module (DLL, BPL,...) EurekaLogExpert290.bpl try to load.

You may either measure the time for both way of doing it, of look at the assembly code generated.

Maybe your are wrong. With dcc64 compiler, Integer is 32 bits and NativeInt is 64 bits. Either define varindex as a NativeInt, or use a cast for count (You cannot have more that 2^31 index in that case).

You can specify default parameter values in a procedure or function heading. Default values are allowed only for typed const and value parameters. To provide a default value, end the parameter declaration with the = symbol followed by a constant expression that is assignment-compatible with the parameter's type. Parameters with default values must occur at the end of the parameter list. That is, all parameters following the first declared default value must also have default values. function GetWeekDates(const GivenDate: TDateTime; out startDate, endDate: TDateTime; const SOWDay: string = 'SU'): Boolean;

Please post in English. Use Google Translate if you don't know English. Edit your message to make it in English. Thanks.

It works seen from here. Does it works for you?

That's not how to remove a program. You should have used the installer to remove it because there are many other things (registry keys for example) and other folders. Now you must find all references to the old program and delete it, including hidden files and folders. Do that with administrator privileges.

That's correct. Embarcadero want CE user to use the latest version of their product. Anyway, why do you want to use an older version? btw: if you BUY a license, then you may install older versions, even in parallel.

Does the old "control panel" still work? The Win+R, then enter control in the input field then Enter key.

Which tablet is this (Brand and model)?