Lajos Juhász

You can query the state of these buttons using https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-getkeystate if GetKeyState(VK_CONTROL)<0 then .... if GetKeyState(VK_SHIFT)<0 then ....

Same for me. I don't have the registry entry in the AppCompatFlags\Layers. Delphi 12 works just as should be with a normal level user without beeing elevated.

The first instance of bds should debug the second one. Thus, it should break on the error and show the call stack. The last Delphi version where I have had problems that required to debug a second instance of Delphi was XE5. In Delphi 12 I compile without runtime packages and have a limited of debugging this kind of errors.

Select the package and from the main menu activate Run - Parameters. For host application you shoulds select bds.exe (default location is C:\Program Files (x86)\Embarcadero\Studio\23.0\bin\bds.exe). Hit F9 a second instance of Delphi will start in that instance open the package and try to install. You should get a call stack.

The product About page gives you an explanation. According to that page it is an automatized robot that can analyze and rewrite your code. In my experience that is a very bold claim.

I've copied IPADresses you posted and using the i.ReadString('DBiDashboard', 'IPAddresses', '') cannot reproduce your problem.

It's not a Captcha it is a test for AI. Only advanced AI can fill this questionary.

Correct the IDE. The question was if using ISO and WEB installer will behave differently.

Same question for me.

For me this is the first time that I am using a standard user, the IDE works without a problem. I have the default UAC for standard users, that is Always Notify.

I am using ISO to install Delphi, never have had to start it elevated.

To get the access violation I have a simple example. I do not know how to create a bug report. If you try to connect the show dialog to the merge element. (I guess it is not supported, but killing the IDE is not acceptable behavior.) ---------------------------------------------------------------------------------------------------- Using copy paste I have managed to break the code generation (the last show message - thank you is missing): Also, for some reason the files are not generated: [dcc32 Fatal Error] mainFRM.pas(25): F2613 Unit 'Test.M1.V1' not found. What I dislike in the code is that everything is an inline variable. If you have a decision (if then - else structure) the elements after the merge point are generated inside every branch. I have had no time to test it in detail (I will have more time next month).

It generates a code that you can call but cannot change. If you change it will be rewritten the first time when the new code is generated. Note. I find the generated code unreadable and can kill the Delphi IDE with stack overflow.

It is in the e-mail you going to receive. Interesting on the installation that it doesn't support limited users, to install it you must run the installation as administrator. When the install is finished the limited user will not get it in the IDE. The solution is to install it outside program files where your user has write access.

Sometimes a logging can help. Log the start and finish of every action you take when the menu is executed (starting loading this / finished, starting that / finished). The part that does not have the finished event in the log is caused the hang.

I cannot, fortunately copilot is ready to help us out. Here is the response: It sounds like the author is discussing their experience with Delphi, a programming language and software development environment. Here's a breakdown of what they're saying: • "As what happens on the DPR I just edit (fix) the DPR and compile.": DPR files are Delphi Project Files that contain source code. The author seems to be saying that they usually edit or fix the code in the DPR file and then compile ithttps://stackoverflow.com/questions/13734278/opening-delphi-project-files-any-downside-of-opening-dpr-instead-of-existing-d. • "I moved from 7 to 10 where it started happening": This likely refers to the author upgrading from Delphi version 7 to Delphi 10. They've encountered some issues since this upgradehttps://stackoverflow.com/questions/13734278/opening-delphi-project-files-any-downside-of-opening-dpr-instead-of-existing-d. • "It seems I am not the only one.": This suggests that other users have experienced similar problems after upgrading their Delphi versionhttps://en.delphipraxis.net/topic/11566-drag-and-dpr/. • "Where is Embarcadero then?": Embarcadero is the company that develops Delphi. The author is probably asking for support or an official response from Embarcadero regarding the issues they're facinghttps://www.embarcadero.com/Support/. • "P.S I have been with Delphi since #1": The author mentions they have been using Delphi since its first version, indicating they have a long history with the software. If you're experiencing similar issues, it might be helpful to reach out to Embarcadero's customer support or check their support forums for assistancehttps://www.embarcadero.com/Support/. Additionally, it's always a good practice to back up your projects before upgrading to a new version to prevent any potential loss of work.

AFAIK this can be done only in code.

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.