DelphiUdIT

nothing ... already answered ...

LOL, I miss we are in a P4D section, sorry. I cannot help you , I never used Python4Delphi.

I don't know VTK, but I don't think that is a revolutionary approach to "surface" drawing. In the web nothing about Pascal, Delphi or FPC related is available. Surely it's needed a handle to a graphic window. And should be a function that assign this. Start from here. If there is something about "C" or "MFC" sample, will be available usefull info.

Apart from the fact that we are in the section: nothing else.

But he's asking about C++, doesn't he ?

I'm sorry, I miss SSL version ... But on 2008 (the packet that he indicate) OpenSSL in use was 0.98 ... only two years later OpenSSL 1.0.0 was published. And ICS surely (or not ???) didn't had TLS "implemented" with OpenSSL 0.98. So, may be that is working with old ICS and new OpenSSL but with SSLv3 protocol. But that is my thinking, for sure he should upgrade his environment.

If you have the community edition, FastReport component is not available. Six years ago (2018) there was an edition of FastReport for CE, but now you must buy it. I never used PowerPdf.

@Graphic Equaliser You are using a too old SSL library. May be you are using 0.9.8 OpenSSL and those are the ciphers used: only the SSL_v3 is supported. You will not be able to connect to any site, 'cause your software should use TLS protocols (TLS1.3 or TLS1.2 should be the best). You must upgrade to a new ICS package. Try to use the Community Edition of C++ or the free command line compiler : https://www.embarcadero.com/free-tools/ccompiler

Thanks very much. I knew that the source is not public available, but I was hoping the DLLs could be distributed.

This is in Italian, you must go in "Settings/Networks an Internet", there is a "casual hardware address" setting ... if it is set I think that for every connection Windows generate a new MAC ...

I (can) have the OpenSSL binary for Windows 64 bit and Linux 64 bit, version "1.0.2zi" of 20/09/2023. Only two CVE is missing ad this time ( CVE-2024-0727 and CVE-2023-6237 refer to: https://www.openssl.org/news/vulnerabilities.html ) and they are classified low severity. With this release everyone use Indy are updated with security, waiting for the Indy 11. OpenSSL 1.0.2zi remediates the following CVE's: CVE-2023-3817 CVE-2023-3446 CVE-2023-0465 CVE-2023-0466 CVE-2023-0464 CVE-2023-0286 CVE-2023-0215 CVE-2022-4304 CVE-2022-2068 CVE-2022-1292 CVE-2022-0778 CVE-2021-4160 CVE-2021-3712 CVE-2021-23841 CVE-2021-23840 CVE-2021-23839 CVE-2020-1971 CVE-2020-1968 CVE-2019-1551 CVE-2019-1563 CVE-2019-1547 CVE-2019-1552 CVE-2019-1559 I don't know if I can share those library, since OpenSSL nothing say about binary license ... may be @Remy Lebeau can suggest if i can post them here. Remy can post also the libraries in the Indy official repo.

In one of the document they say: Really ? JS is a memory safe languages ? Who exposed this ... You can use a variable before declared ("hoisting") ... this is safe memory language ?

Like I told in prev. post ("Autorizzazioni" is like "Permissions" in Italian). But HKLM is accessible (the OPEN in READ mode seem to be OK from her), for this she must see the ERROR code in the query function ... is about "key not found" ? or "access right" ? or ???? This is sure a new security counter measure from new Windows Server (or in the IIS) and should be interesting to know how the rights are on site.

She is try to reading the HKLM, this key is always present and is the same for all process (of course not in a virtual machine).

Value := RegQueryValueEx(Key,PChar(strValueName),nil,nil, @Buffer,@Size); This function return a value. Log this value, that can show you what is the EXACTLY the problem. From line 11867 in WinApi.Windows.pas (Delphi Athens 12 patch 1) you'll find what's means that code. Probably is like @Kas Ob. say, you cannot read HKLM registry from ISAPI. If that is the problem, you must transfer all the key you need from HKLM to HKCU (or the right root key). P.S.: another solution is that you give full access right to the registry key that is interested to your read, use "regedit" for this and with right mouse click on the key choose "Autorizzazioni" (I think you are Italian 😉).

What kind of ERROR report these function ? May be that information can help you.

It is not strictly related to the use of TLS 1.3 but rather to the use of the new SSLs (we are now at 3.x), given that the old ones (which Indy still uses) have been deprecated and therefore could represent a security risk. It must be said that with the PR version of the Indy repository which supports OpenSSL 1.1.1, you can also use OpenSSL 3.1.x not for all the functions but for a good part (which is the one that interests the SSL functionality of a WEB server for example). Actually I have a WEB server with Indy and SSL 3.1.4 on Windows.

May be is related to this https://docwiki.embarcadero.com/RADStudio/Sydney/en/Visualizers but I don't think that there are the source code available. There is a ToolsApi about that: https://docwiki.embarcadero.com/RADStudio/Athens/en/Debugger_Visualizers

Uhmm, may be I'll probably say bullshit, but you can import assemblies from .NET only if they are flagged as COM compatible (they must be compiled in this way from Visual Studio). Others way are to use some instruments like CrossTalk or also JCL (from Jedi project). But I don't think that you will able to import like a component, only to call them like a DLL. You can also use some open source software like " ILSpy, the open-source .NET assembly browser and decompiler" to analize the .NET DLL. OF COURSE YOU MUST HAVE THE RIGHTS TO DO SO !!!

There are already know components on the fly without to work for new ones. For communications, one of the standard that works on serial COM, TCP and UDP is ModBus. With that you can communicate whatever you want, ghost I/O, virtual I/O, GPIO and others. Surely there is a ModBus implementation for STM32 (this one for example: https://github.com/nimaltd/master-modbus ). But, if you choose a STM32 with BLE, also BLE stack should be and you can create GATT service (so no physical connection for communication). You miss to read my full post: the communication is simple, the construction of full environment is more complex. EDIT: of course, for Delphi side there are also ModBus implementations (I think I posted here about this).

Communicate with STM32 device is one thing, program a STM32 device is TOTALLY another thing. To program a STM32 (in IDE way) is like to construct a "Delphi Builder" for c language (I mean like Dev C++ that is made with Delphi) mixed with typical automation / building functions and so on. Instead, to communicate with STM32 is simple. There are many options. But I (we ?) don't understand what is your objective ? I think you desire a environment like some "Automation Builder" and with that you want to program a STM32 device, but this is like construct an new IDE and not a simple communication. Other solution is to have a "base" core support with API in STM32 and you construct you application around those API.

Seems that you populate your controls for an automation / building application. It' necessary to view the values with a combobox ? You can use a label (or other simple control) for every field and when a user click in one of them you can propose a combobox to change the present value or numeric keyboard or others custom control.

I don't know if XE5 is the useful tool for producing WEB apps. But it was released over 10 years ago, I think that since it involves updating software perhaps you should upgrade to the latest version (or at least to a more recent version). now in addition to the TRIAL version which allows you to carry out a time-limited trial of the Architect version of Rad Studio, there is also the Community Edition version which is free within certain limits: link for the license and conditions of use: https://www.embarcadero.com/products/delphi/starter In this link you can see the features of the individual commercial editions: https://www.embarcadero.com/docs/rad-studio-feature-matrix.pdf I don't think you can use the XE5 if you have bought XE3. You must discharge it but probably the license will not be activated during installation. P.S.: take care that Embarcadero is updating all they server and services, so is possible that the community edition is not installable at this moment.

RFC 5322 was updated to RFC 6854 in 2013. In the Indy sources the last comment is on the RFC 2822 regulation (obsolete and replaced by RFC 5322). However, it is known that the comments have not been updated, nor have the existing manuals and docs been updated. The only one who could answer you is @Remy Lebeau This is also a discussion about this argument: https://stackoverflow.com/questions/25576292/indy-smtp-server-how-to-detect-cc-bcc-recipients

Inside the program I have a thread that runs independently and keeps the timing of a cyclical event controlled, let's call it the end of the processing sequence (normally a processing cycle lasts around 150 ms.). In all my programs, I generally work on events, the application must react to a given event (reading data from a PLC, receiving an image from a camera, etc ...) and if this does not start the thread goes to monitor the device (or devices) from which input is expected to verify that it is online (if there is no "keep alive" possible). Then every certain time I launch a simulated event to verify that the processing chain is up and running. All devices that have the capability (even devices intended as software, for example third-party applications), MUST launch a "keep alive" towards the application (and also the opposite) to confirm the online operating status: the KEEP ALIVE can happen via TCP or UDP, via physical inputs or various other mechanisms (for example with some third party applications there are COM Object events). In addition to all this, the thread also checks the memory used by the program to verify that it does not exceed certain limits (when a program runs for months without being turned off even a single byte of leak "every now and then" becomes a problem), and the temperature of the CPU package. When possible, following a persistence of high temperature (> 92 degrees) slows down the entire process to check for anomalies in the thermal dispersion of the PC. The application is launched from a ".CMD" batch file which checks the return value of the application and if it is different from $127 (for example) it relaunches it again. The monitoring thread or any other unhandled exception generates an EXITPROCESS($0) or sets the EXITCODE to $0 (depending on how severe the detected anomaly is). The normal exit of the program instead generates an EXITCODE at $127. The same monitoring thread sends an email and writes a log to report the anomaly.