Lajos Juhász

It's the same as you Embarcadero account.

It's hard to verify code this large. One thing you're for every step create a query: gisShapeTypePolygon: begin qryUID := TADOQuery.create(self); This is not going to be a definite leak as it has self (most probably the form as the owner). The query will remain open until the owner is destroyed.

That's not what I have Size: 1.80 MB (1,894,304 bytes) and my coy was signed by Idera, Inc.

Yeah, and breaks FireDAC as it converts from UTF-16 using the language for non-unicode programs instead of using conversion from client locale to server locale.

This is true for strings. However in the example it's used to assign the value to ansistring: var MyAnsiString: AnsiString; AnsiString is not a unicode string thus there is no chr(11200) most probably the code page of the ansistring will have no conversation for that unicode code point thus will be converted to ?

At least I won this bet. You should always post the parent class as don't everyone will have the complete source. By openning the System.Classes.pas it's clear what to do: procedure TCustomMemoryStream.SetPointer(Ptr: Pointer; const Size: NativeInt); change the method signature to match.

You should at least provide a compiler error message. From here we don't know which class it's inherited from. I don't like to gamble but will make an exception my guess is that you should change the parameters of the method to match the signature from the parent class?

Delphi 11 can be tough on debugging. I also have problem to debug a code in a package. Sometimes I can place a break point and works as expected sometimes I have to use ShowMessages to debug. Build all can help (but not always).

Without seeing a code the UI reading from a working thread could be a problem as that must be synchronized. The working thread should post information or synchronize with the UI.

Most probably there was no QP ticket to implement this logic?

You can find out in the Help: Use debug .dcus The debug DCUs contain debug information and are built with stack frames. When this option is checked, the compiler adds the debug DCU path to the search paths specified in Debug Source Path on the Embarcadero Debuggers page.

Open a ticket at https://quality.embarcadero.com/ with the steps how to get Access Violation.

Yes you can, before you compile the package uninstall all the packages that depends on that one. That should improve the situation. Unfortunately this is a "known" issue and impossible to report (as it's hard to make the required test case). PS. For a project group I even have a situation that some days Access Violation is almost every time triggered when I compile an application without runtime packages.

uses Xml.XMLIntf, Xml.XMLDoc; procedure TForm1.Button1Click(Sender: TObject); var MyXMLDocument : IXMLDocument; FounderNode : IXMLNode; begin MyXMLDocument := TXMLDocument.Create(nil); MyXMLDocument.Active := true; MyXMLDocument.Version:='1.0'; MyXMLDocument.DocumentElement := MyXMLDocument.CreateNode('ab', ntElement,''); MyXMLDocument.DocumentElement.DeclareNamespace('xsi', 'https://www.guru99.com/XMLSchema-instance'); MyXMLDocument.DocumentElement.DeclareNamespace('xsd', 'https://www.guru99.com/XMLSchema'); MyXMLDocument.DocumentElement.SetAttributeNS('xmlns', '','MyString'); FounderNode := MyXMLDocument.DocumentElement.AddChild('founder'); FounderNode.NodeValue:='Krishna'; MyXMLDocument.SaveToFile('TestOne01.XML'); MyXMLDocument.Active := false; end; You have to set the version and MyString should be the 3rd parameter not the second one.

There is a hope for Delphi 11 CE; my bet is that it's going to be released after Delphi 12. In order to learn more about the release date and roadmap I suggest to apply for a job at Embarcadero (that's the only legal way to get information).

You can access the windows handle using WindowHandleToPlatform. .

Google thinks this is a way to achieve it: https://www.advancedinstaller.com/forums/viewtopic.php?t=9364

This should be part of the installation of your application. For example Inno Setup can do it for you.

Make your application DPI aware and the dialog should be same on every settings.

It's not. There were Embarcadero webinars on this topic.

https://docwiki.embarcadero.com/RADStudio/Sydney/en/Conditional_compilation_(Delphi)

You can also test with regular VCL controls, the bug could be also in the DevExpress controls. With VCL placed on the form I don't have had placement problems.

It's fine until you get an exception, which will result in a memory leak.

Never had deadlock when using amblocking. On the other hand in D11 sometimes amCancelDialog will not work on query. You must change for the connection before and change back after the query is finished.

(I believe earlier if you have had no valid licence there was no possibility to renew the previous one. The only option was to buy a new licence.)