FPiette

Maybe the answer is in this article : https://blogs.embarcadero.com/new-in-getit-aws-sdk-for-delphi-and-edgebrowser-updates/ Also interesting: https://learn.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution

This message means the compiler doesn't find ReceiveTB method implementation. Since it has been introduced not long ago (In V8.70), I suspect you have and old OVERBYTEICSWSOCKETS.OBJ hanging somewhere in the search path. Or maybe C++ compiler doesn't understand correctly the overloaded ReceiveTB method? I suggest you create a test application having a single form with a TWSocket and TButton dropped on it and a call to both overloaded version of ReceiveTB from the button's OnClick event handler. The code doesn't need to do anything useful neither to run correctly. The goal is only to understand with the simplest code possible if the compiler and linker understand/find ReceiveTB method.

That doesn't answer all my questions.

Look at this: https://github.com/WouterVanNifterick/C-To-Delphi Which pascal dialect do you need? What part did you already have done? There are dependencies you' have to port as well. At first glance what you ask looks like a huge task. What would be your benefit? Can't you just compile the C code?

Could you try with one of the sample provided with ICS? And/or create a simple test project with only a single form and a TWSocket component dropped on it, nothing else? Make sure you use ICS from the latest nightly snapshot or from the SVN repository.

Looks like you have two ICS versions.

Not directly possible. If you explain why you think need that, and given an example of usage (the call!), maybe we can give a better answer...

No, you are doing wrong. You are making a shortcut. 98% of Delphi users don't care about math speed for what they have to do with Delphi.

One may create an issue at the GitHub repository just to ask for licensing.

Probably 98% of Delphi users don't care about math speed for what they have to do. Only those doing math intensive applications do care. So you care and Patrick doesn't, me neither

Yes, a packed record is the way to go to control memory layout as much as possible.

That would be a great idea if you update the repository once you updated the code for Delphi 11.

Look at the documentation! It is available from https://www.nevrona.com/download/ You need to have a license. Contact them if you can't find your license anymore. Don't ask use to help you make an illegal use of their product.

The download link is: https://www.nevrona.com/download/

Well, how do you explain that a .PAS file actually contained JPG data? If you have not renamed, you copied a jpg over a pas file. btw: There is no shame to make an error. That's how we learn.

Just find the unit. For a better answer, explain the context !

@georges pletinckxI'm interested to know if - as I guessed - you had renamed a JPG file to .PAS.

You probably need to right click on "design" packages (win32 platform only) and select "install" in the popup menu.

@KodeZwerg That is basically the same answer as I gave yesterday... He probably got a screen dump of the source code as a jpg image and renamed the file to .pas thinking this is the way to get the actual source code 😄😄😄 Of course it isn't...

It looks like you Calcul.pas file is not a Delphi source code. Given we see "EXIF", it is possible that it is a JPG or other image format. If you open Calcul.pas using Notepad, does it display garbage?

I project / Options / Delphi, change "Output Directory" to whatever you want. You should also change "Unit output directory" which is where the DCU are going. It is better to use the macros $(Platform) and $(Config) so that the destinations are different for all platforms and configurations.

What are the error messages you get?

Run your application under the debugger and set a break point on the line "FTimer.Enabled := True;". Check FTimer value. It is likely FTimer is nil at that moment. Show the code in your component source code where you create the TTimer instance.

I wrote a simple shell property sheet handler using Delphi 11. It works perfectly when I register it for all file types. But it does nothing (My property page not shown) when I Register it for a specific file type. Registration for all file types: // Error handling removed for clarity Reg := TRegistry.Create; Reg.RootKey := HKEY_CLASSES_ROOT; if Reg.OpenKey('\*\ShellEx\PropertySheetHandlers\MyDelphiPropSheetHandler', True) then begin Reg.WriteString('', ClassID); Reg.CloseKey; ClassID is registered as part of the COM server. This is done automatically by Delphi RTL. Registering for a single file type: I simply replace "*" in the above code by the file extension which is ".arw" in my case: // Error handling removed for clarity Reg := TRegistry.Create; Reg.RootKey := HKEY_CLASSES_ROOT; if Reg.OpenKey('\.arw\ShellEx\PropertySheetHandlers\MyDelphiPropSheetHandler', True) then begin Reg.WriteString('', ClassID); Reg.CloseKey; This simply does nothing. No error, just nothing. The key is correctly written in the registry. What am I doing wrong?

My experience (Win11) shows that it DOESN'T WORK for some file extension, specifically the one that was my target (.arw).