Lajos Juhász

That should be easy, consult the AI.

When you create a detour you should store the original function address to be able to return it. we don't know what createNewDetour is doing (it is not part of DDetours that was suggested).

First step is to create a backup of the original dproj. This is required to be able to copy the required settings for the project that is written in the dproj. If you delete the dproj and open dpr Delphi will create a dproj with default settings. You can try to compile it (depends on your project it might be successful). If you cannot compile the project with the new dproj you will have to add required paths to the project until you can compile it.

Bad packaged unit format: The error is: E2213 Bad packaged unit format %s.%s (Delphi) https://docwiki.embarcadero.com/RADStudio/Alexandria/en/E2213_Bad_packaged_unit_format_%s.%s_(Delphi) In this case it is looking in the vcl.dcp and looking for vcl.forms both the dcp and the unit exists in Delphi. It could be a search path issue, damaged dcp or failed compilation on the source. In earlier versions when I got similar errors the solution was to compile every package that my application uses. Then the error magically disappeared (in those cases the compilation never failed, however the compiler failed to locate the correct files. A 32-bit application that uses runtime packages).

That is correct.

No VCL application should try to compile DesignIntf.pas it is a violation of the licence. Only a runtime package can use it.

Unfortunately not enough details. If you get this while you are compiling a design time package you should add designide to the required section. DesignConst is still part of the Delphi (it is located in the source\toolsapi folder). Make sure that any runtime package does not use the designide.

You should read more about memory managers. The memory manager will not always return the allocated memory to OS. It's not only Delphi but every single other language works that way. You can google it easily.

During the debug you must get a call stack.

I saw this in Delphi 11.2, whenever I open those files in D12.1 it removes them.

In that case you will have to implement it yourself.

Why are you unhappy with Embarcadero if you have permission problems with your regular account?

Also until developers did not start to use multiple languages.

I don't have Android platform at the moment. On Windows you can change the scale.y to a value <1 to get a smaller trackbar.

During code review I can find cases when the developer assumes that the strings are zero based.

The mobile platform was a failed experiment to move string to be zero based.

I can confirm that it does work.

There is only limited information here: https://docwiki.embarcadero.com/Support/en/“ERROR_ITMS-90507:_Missing_Info.plist_value._A_value_for_the_key_'DTPlatformName'_is_required”_when_submitting_an_app_to_the_iOS_App_Store

With no 3rd party installed it is very fast, I get the list instantly. Get a cat, dogs are boring.

Compile the fmx application for windows 32 platform. (Unfortunately) The (only) most stable platform to debug delphi application.

It really depends how many Delphi versions you have to support. The change is documented and was made to make life easier to integrate with other programming languages. Mora information: https://dalijap.blogspot.com/2023/09/coming-in-delphi-12-disabled-floating.html https://docwiki.embarcadero.com/RADStudio/Athens/en/Floating_Point_Operation_Exception_Masks

A more details could help. One solution can be to place a panel onto the form where you place your UI controls. If the record is lock set the enabled proprty of the panel to false.

It was a request to change the exception to a proper message before Embarcadero included it in D12. Unfortunately the answer was it is a known limitation of Delphi.

The paint method is to paint on the canvas not to set a property value.

During the Paint method you have to handle csPaintCopy in ControlState (you can check in Vcl.DBCtrls).