Leaderboard

That's exactly what I am doing, since the packages are plugins that the user can choose not to load. It's no where near as simple as you make out. And really, my code and application architecture is not the issue here.

That's what QA said before 10.4.2 released

I found the answer in this post https://en.delphipraxis.net/topic/2258-need-help-adding-namespaces-to-soap/ InvRegistry.RegisterMethodInfo(TypeInfo(NAV_ExportCustomerItemPriceV1Soap), 'NAV_CustomerItemPriceV1', 'ReadMultiple', '[ReturnName="NAV_CustomerItemPriceV1Result"]', IS_OPTN); Params are: TypeInfo, InternalName, ExternalName, ReturnName, XMLOptions Setting ExternalName appears to have fixed it

I am afraid that list might be too long... and it would require input from large number of developers. It all depends on code you have and what kind of workflow you have at any given moment and for which platforms you develop. What is good version for some people, might be utmost nightmare for others. And besides stability, there might be other reasons and bugs in the core frameworks which makes some versions unsuitable for some developers. Workarounds were usually move to another version and hope for the best. Without actually trying on your own code and working with some version, one can never know. Since Embarcadero opened up beta testing for larger audience, it would be good that anyone who can participate. The more the merrier. It is also important to start testing early, because some bugs if found too late in the cycle may end up unfixed. Of course, all that also does not guarantee final quality and release success, but it can be significant factor. Literally one person can stumble upon critical bug that would end up in RTM, and all other testers might miss it for one reason or another. It is huge codebase, and we cannot test and use all features thoroughly.

https://delphisorcery.blogspot.com/2021/04/testinsight-12-released.html

And now a patch for 10.4.2 is released!

Or he just wants to see the correct values when inspecting them while debugging?

Not safely, no. Is it legal to have a cross-process parent/child or owner/owned window relationship?

I believe Remobjects Hydra can help you with this. If you go to https://hydra.remobjects.com/hydra/tour.aspx, you can see there is a section "Combining VCL and Firemonkey" .... Hydra provides a solution for this problem by allowing developers to integrate FireMonkey UI seamlessly with their existing VCL applications, or conversely add existing VCL user interfaces into new FireMonkey apps. ...

This is way more complicated than you might hope. Your VCL app will run a message loop that is designed for VCL. It's not going to be able to service your FMX form. I don't expect there is a simple solution. btw, INVALID_HANDLE_VALUE is for HANDLE types, i.e. THandle in Delphi. For an invalid HWND use NULL, which is 0 in Delphi.

You can join the beta if you are on active subscription. Most recently, betas were announced on Embarcadero blog posts like this one https://blogs.embarcadero.com/delphi-and-cbuilder-10-4-2-beta-invite-for-update-subscription-customers/ Invitation is also probably sent or announced through marketing emails. You will have to sign NDA and you are not allowed to discuss participating in the beta nor about any features, fixes or bugs. Above is valid for major release beta cycles and updated. Patches and hotfixes are commonly tested by smaller number of people because testing cycle is shorted and focus is on particular bugs. If you have some particular reason for testing some hotfix or you have some major issues using latest release, you can always try going through official channels and present your case. However, there is a catch-22 because you will never know whether some testing is in progress or not, and even when there is, you might not get answer to that question even when you ask directly (not in public). Next major release will be 10.5 and at some point you can expect posts (unless policy changes) inviting subscribers to participate for that beta. When will that be, nobody knows. For now you can just wait.

@Rollo62 Hi , sorry it took a while , but I just continued development on this tool which requires auto start with the custom .dex And debug is working! I am using Delphi 10.3.3

Are you volunteering to rework my application architecture if it's that easy - I have 100+ package projects in a project group, a few dll's and 4 exe's (around 4M lines of code) and I see these errors all the time. I cannot use LSP at all because of this, but even with it turned off the IDE and the compiler are unstable. I can't afford to spend months refactoring my code in the hope that the IDE or compiler might then just behave correctly 🙄