I don't know what the "Ex" is good for (it does look rather Windows-centric although there is a conditional directive for compilation on Windows.)
TMPHexEditor is a TCustomGrid descendant to view and edit binary files in hexadecimal and textual format.
TMPHexEditorEx is an advanced hex editor, is supports OLE drag and drop, printing, print preview and more.
[...] there is a compilation error because function "RenameFileUTF8" is not found in unit mphexeditorex.pas. Add unit "LazFileUtils" to the uses clause of unit mphexeditorex.The author has accepted and applied my merge request to fix the compilation issue. Now the package should compile correctly "out of the box".
[...] there is a compilation error because function "RenameFileUTF8" is not found in unit mphexeditorex.pas. Add unit "LazFileUtils" to the uses clause of unit mphexeditorex.The author has accepted and applied my merge request to fix the compilation issue. Now the package should compile correctly "out of the box".
Have you tried to apply the fix I proposed? In this way I solved the compilation problem.
Or download the package from the author's site again (https://github.com/michalgw/mphexeditor), the error should be fixed now.
This patch is not good, it works only with FPC trunk or 3.2, but not with 3.0.4 used by the Lazarus release versions. The point is that the older versions still require the "const", but fpc 3.2+ require the "var".Fixed. Thanks!
Just for curiosity: What change in the next major release of compiler cause such a break in backward compatibiity? I'm a little worried for my code base.I can't find a reference for it any more, maybe it was a bug report, I think assigned to marcov. It was exactly this function declared in unit ActiveX where the "const" was replaced by a "var" for Delphi compatibility. If your code uses ActiveX/OLE etc you should test whether it compiles with FPC-trunk (or with still unreleased FPC 3.2)