Lajos Juhász

You should try these steps to report the bug using the e-mail to protect the source code you are working on: https://docwiki.embarcadero.com/RADStudio/Athens/en/Troubleshooting:_Delphi_LSP.

Something is blocking the file(s) from writing. Check out for viruses and settings in applications that could lock the file, is it a shared folder? First step could be to add the folder to the antivrus exception folders lists to keep it locking the files there.

in general, when using with you can never sure to which object you are assigning a value. It can work in one version of Delphi and break in the next one. You can always write: var a: TFDAggregate; begin if Qry.Aggregates.Count = 0 then begin a:=Qry.Aggregates.Add; a.Expression := 'COUNT(Town)'; a.Active := True; a.Name:='NoName'; Qry.AggregatesActive := true; end; end;

First of all do not use with it is always a bad idea. You are not setting the name property for the aggregate object. Edit. I have checked even the examples on docwiki are wrong.

You can send the query as a parameter to the function that generates the XML.

Most probably yes. It would be easier if we could get that information. I do hate when on codebase I am working on changes like this does not have a comment with a proper description or ticket number. Searching in repository for the specific change can be time consuming.

Maybe it is commented out to fix some strange issue/bug. In that case the developer that has commented out the code should include the report number in the comment to document the change in behavior.

You can try the test 64 bit Delphi IDE.

Same on my system 2 different exe files.

It could be that when the library detects the debugger it slows down. You can try using Lazarus at Windows to see if it behaves the same.

The question was whether it is possible to check if the future is completed or not. Method Wait can be used to achieve that. (The design of wait could be improved to support non-blocking call, but we can argue if a couple of ms delay is significant or not.) Nobody mentioned that the future is going to be used in the main thread. Whenever ProcessMessages should be used or process paint messages depends on how long the calculation should take. If it is under a minute or the application should be blocked during the life of the method, it should not be used.

Read the documentation: function Wait(Timeout: Cardinal = INFINITE): Boolean; overload; You do not have to wait for infinite.

That is the idea behind future to do something until you definitely need the result of the future. If you want to check if the future is finished you can use the wait method.

The answer is the same as for the previous question you have to change the StyledSettings. In this case you are changing the Family and Style thus you have to remove those elements from the set, you do not change the Style of the font. You can replace: L1.StyledSettings:=L1.StyledSettings-[TStyledSetting.Style]; L2.StyledSettings:=L2.StyledSettings-[TStyledSetting.Style]; with: L1.StyledSettings:=[]; L2.StyledSettings:=[];

Calling a method of the target form?