Jump to content

DelphiUdIT

Members
  • Content Count

    822
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by DelphiUdIT

  1. DelphiUdIT

    Documentation links on indyproject.org not working

    All links seem not full working. Look this, extract with 7-ZIP (Explorer give me an error): https://github.com/IndySockets/Indy/files/7782730/IndyDocs_10.1.5.0_HtmlHelp.zip
  2. DelphiUdIT

    Documentation links on indyproject.org not working

    Indy Wiki is here, and is working: https://github.com/IndySockets/Indy/wiki And if you have Rad Studio installed you have the offline documentation (Help/Third-Party Help/Indy Library Help)
  3. What is the target of your application ?
  4. This is available on OpenSSL 1.0.2u, the last SSL available that works on Indy bundle with Rad Studio. You are using SSLv3 this is deprecated and should not be used. YOU MUST USE TLSv1.2. Set IOHandler to use TLSv1.2 (in the options): SSLVersion := [sslvTLSv1_2]
  5. In Indy, the valid chipers type accepted by a server connection is setting through the TIdSSLOpenIOHnadlerServer.Options.ChiperList property, for example: //For TLSv1.2 handshake CipherList := '!EXPORT:!LOW:!aNULL:!eNULL:!RC4:!ADK:!3DES:!DES:!MD5:!PSK:!SRP:!CAMELLIA'+ ':ECDHE-RSA-AES128-GCM-SHA256'+ ':ECDHE-RSA-AES256-GCM-SHA384'+ ':ECDHE-RSA-CHACHA20-POLY1305'+ ':ECDHE-ARIA256-GCM-SHA384'+ ':ECDHE-ARIA128-GCM-SHA256'+ //Weak but used in old products ':ECDHE-RSA-AES256-SHA384'; Search in the property of DataSnap components for IOSSLHandler and set this property. This is correlated to "certifcate file" and "certificate private key" (CertFIle and CertKey property of the Handler).
  6. You can try also with https://prog.olsztyn.pl/paslibvlc/ It has the ability to play stream audio and video, but you need VLC installed on system.
  7. DelphiUdIT

    Could not load OpenSSL library.

    But not this time .... Datasnap is working with Indy REPO too .... there are some things to do, expecially one ... was missing from my (sparse) instructions and I never had any issue (never used DataSnap). These three lines must also be copied into the "library path" and DataSnap will "start" working again. Start from previous link posted.
  8. DelphiUdIT

    Could not load OpenSSL library.

    I think was better to create a new topic under "Indy" section. Your issue has nothng to do with this topic. But, if you install new Indy from official repo, you have to build it with all the modifications about the packages and you must rebuild also the optional components, wich sources are distribuited with Rad Studio and not present in Indy REPO. Read this for more information: Take care that replace the Indy bundle with Indy REPO can invalidate some components (from Embarcadero and from third parties). If you have third parties sources you can recompile and rebuild them. EMS components and Datasnap use Indy under the hood ans so is possible that they don't work with new version of Indy.
  9. But they produce SSD too, and the test that they made were about their SSD. I don't think they have any interest in "cheating" on the results. It could be that technology will move the "hand" one way or the other over time.
  10. https://www.kingston.com/it/blog/pc-performance/what-is-ram-disk
  11. It could be that an alien has taken over his body... or his account....
  12. DelphiUdIT

    Sqlite Delphi 12 linker error

    I really don't know if this can help. but you have tried to do "REVERT" action:
  13. Be careful when interpreting "objects", whether they are properties, variables, or other. Granted that as you say there is only one assignment, you do not know what an assignment can trigger. And the same encapsulation paradigm makes sure that the true nature of the property is hidden from you (it can be a reading of a variable, a writing, a function or triggering a series of delayed and events). Try to think what "triggers" a simple assignment of a property such as a connection to a DB (...Connected := True;). It is necessary to document yourself, in the absence of experience. This must always happen when dealing with a new topic.
  14. DelphiUdIT

    Event handler in thread

    Don't worry, when you feel the need just ask. Someone will help you. You'll find that Delphi (Pascal) will help you on the way. Also try to have a quick read about the various topics in the various manuals available, there are several available even for free. You can also do a search on the forum and you will find several links about this. Embarcadero's online wiki can also help you. Enjoy and good works.
  15. Look at this: https://docwiki.embarcadero.com/Libraries/Athens/en/Vcl.Forms.TCustomForm.ModalResult Like @Lajos Juhász said, if you set the ModalResult at value different from mrNone the Form will close when the actual procedure will exit;
  16. DelphiUdIT

    Event handler in thread

    Compared to microcontroller programming, you have to think of an application in Delphi as if it were a stack for microcontroller services: like a Bluetooth stack or a TCP/IP stack. You are building something that has to communicate with other entities, you are building a stack.... Your program has to communicate with all the related entities, starting from the individual "components" that you use. You have to understand that your program is part (if you build it for Windows, but the same conditions apply for other OSes) of an ecosystem that includes some basic functional rules. In your case of a microcontroller, I don't think you have built a TCP/IP stack from scratch, you will use one of those available (among other things, all manufacturers provide at least one TCP/IP stack). With that stack, your code has to "talk" to it and interact. And "things" happen that are not under the control of your code, even beyond the IRQs. With an application in Delphi it is the same, only that instead of interacting within an island (your microcontroller) you are acting within a continent (the Windows ecosystem). You have to learn the rules and basic functions, as you learned to use a TCP/IP stack. But, the world is more bigger than an island .....
  17. DelphiUdIT

    Very large h file to pas

    You need a wrapper in pascal from "HCNetSDK.h" and some dlls: - HCNetSDK.dll - ssleay.dll - libeay.dll - zlib.dll - libssl-1_1-x64.dll for new SDK I think - libcrypto-1_1-x64.dll for new SDK I think Depends on video machine you want to connect you need other dll too, but all of them are in the SDK (may be, in the old sdk they were inside). And of course, all the samples are in C or C# but I think you can copy how they do the things and replicate in Delphi. Of course there is some work to do. EDIT ... or I understand bad and you are talking about CHET ?
  18. DelphiUdIT

    Very large h file to pas

    The last that I had from HikVision was in pure C (and with comments in Chinese ....). They had a C# wrapper for demo project.
  19. DelphiUdIT

    Unicode UTF8 with coded char to char

    This can help ? : https://stackoverflow.com/questions/71288428/encode-string-from-json-utf-8
  20. DelphiUdIT

    Delphi + Windows + isWine

    This is a method to detect if it's running under wine emulation. Look this: https://stackoverflow.com/questions/27413641/how-to-detect-if-delphi-program-runs-in-playonmac
  21. This is the right place, see: https://docwiki.embarcadero.com/Libraries/Athens/en/System.IOUtils.TPath.GetHomePath So your files go to on the home directory or in the subfolder of that like you see.
  22. Have you tried in your deployment settings to set the remote path to: '.\databases'
  23. DelphiUdIT

    Specification IEEE P1363

    I don't have any pubblication about that, but this site use and have an implementation about this standard, may be can help: https://github.com/miracl/MIRACL/tree/master/source/p1363
  24. Hi, if your goal is to be able to "take control" of the project, modify it and implement it with new features, I must warn you that it is an operation that even a senior programmer generates some anxiety. Pascal, and DELPHI in particular, helps you in this and therefore your work will certainly be "lighter". To be able to do this, in the absence of any information about you, there is a series of activities to be carried out preliminarily (what you call a roadmap): 1) Know the basics of Pascal, and by basics I mean the structure of a Pascal program, in particular how it is implemented in Delphi, and its composition; 2) Definitions, variables, constants; 3) Operators (logical, mathematical); 4) Assignments and comparisons; 5) Numbers, characters, variants; 6) Vectors and matrices; 7) Structured data, sets; 8 ) Procedures and functions; 9) Pointers; To then move on to OOP: 10) Basic OOP concepts (encapsulation, abstraction, inheritance, polymorphism); 11) Classes, constructors and destructors; 12) Exceptions; 13) Properties and events; 14) Multithreading; 15) Life and purpose of "variables" or object instances; 16) Memory management; 17) Files, streams; 18) RTL and RTTI; xx) Generics and collections; and lastly (so to speak) to the VCL, if you want to stay in the classic Windows application or in FMX if you want to go towards the environment more dedicated to the Mac, Linux and mobile worlds (Android and IOS), also functional for Windows: 19) Basic VCL classes (TObject, TPersistent, TComponent, TControl); 20) Ownership and parentship; 21) Graphics: TCanvas and handles; 22) Generics and collections; Another topic, really expanded and I would say almost a world in itself are databases ... Delphi has a good library (FireDac) that allows very easy access to most modern and not modern databases. Within all this there should also be a smattering of how the IDE works, already as a "ZERO" chapter as it will be needed to be able to carry out all these points. In conclusion I do not know if there is a specific publication that allows you to do all this, if not it will be necessary to read various publications to allow you to operate safely in the project. This is as far as I think it is necessary, maybe someone else certainly has some additional information or a different path in mind. If the forum members want to provide you with some links on this ... Bye
  25. Normally it works the other way around... you write: {$IFDEF FPC} .... for FPC {$ENDIF} {$IFNDEF FPC} .... for DELPHI {$ENDIF} or {$IFDEF FPC} .... for FPC {$ELSE} .... for DELPHI {$ENDIF}
×