Uwe Raabe

In my Rio installation GenDocCLI.exe can be found in the Delphi bin folder. Also the context menu of the project model has a Generate documentation item. Are you aware that these features are part of Architect and Enterprise only? The Tools menu entry is also missing here. Actually I cannot remember even having it seen before.

Named Pipes may not be the badest decision here. See François Piette blogging about that: Inter Process Communication Using Pipes

Could it be that Z: is a network drive causing that trouble?

DRF is also described here (File Type 3): Delphi Resource File

Sorry, but I am not aware of any option in the Delphi formatter producing the desired output.

Not sure if I've got you right, but perhaps Line breaks before Then is what you are looking for.

In that case, can you check if the dproj files contains the FormType and DesignClass entries for those frames?

Can you upload the dproj file of that project?

The current icons in MMX not only look a bit old, they also don't look well on the Dark Theme. They are not alpha blended and are only available in 16 x 16 pixel size. This may become a problem when the IDE will support High DPI in the future. I am planning to assign a professional icon designer to create new icons matching the icon guide lines of the Delphi IDE. The icons will be alpha blended and are provided in different sizes. They will use the color scheme and style of the IDE icons. You all know that I don't make any money with MMX. Thus I am not able to cover the cost for this endeavor from my private pockets. At least not completely. Therefore I created a MoneyPool at PayPal to collect some donations from MMX users willing and able to spare some money for this special purpose. In case you are willing to donate: Note that you won't get anything for your money (aside a better looking MMX). You cannot expect your favorite feature to be prioritized or your personal bug be fixed any sooner. I promise to spend the money for this special purpose and I will close that MoneyPool when the amount needed is reached. Also I am not looking at the hobby programmer or one man show using MMX, but I guess there are a couple of companies making some profit out of their heavy use of MMX. Perhaps they can shell out a small amount to help here.

While things are already in motion now, I thought it might help to go a bit more public: MMX Needs New Icons – Are You Willing To Help?

Enable Runtime Themes and using VCL Styles are different things. The former is enabled in the Application Manifest settings while the latter is configured in Application Appearance. A Default Style setting of Windows should use the OS Style. Note that both require to Enable Runtime Themes.

How to remove the Upcoming Events panel from the Welcome Page?

Disabling packages usually works on a per project basis. If you want them to be disabled globally, you might be more lucky disabling them when no project is open. BTW; When I want to permanently get rid of IDE packages I usually remove them in the registry under HKCU and HKLM. The advantage is that this approach also works for packages not available in the Install Packages dialog.

In case the plugin adds some entries to the local editor menu: That is no longer working in 10.3! I would link to the QP report here, but I cannot find it anymore - actually I can find near to none QP reports.

Oops - missed the group...

Shouldn't that better go into QP then or did you just miss to mention the report number?

See my comment to Atanas: https://community.idera.com/developer-tools/b/blog/posts/from-the-gm-new-updates-and-changes-to-the-registration-bumps-policy?CommentId=7816b564-c240-4ad1-ad95-a79bdacd479c

I checked the German license and there is no such thing that would a) mention any registration limit in the first place or b) state that increasing that limit is actually part of the support.

I am not sure they would get away with that - at least here in Germany. As long as the customer actually paid for the perpetual license (this excludes the CE), the ability to use it legally cannot be prohibited just because there is no current support contract. At least a reasonable fee for the registration bump would perhaps be acceptable, but definitely not denying it completely.

I have made good experiences with Kassl: OPC FOR DELPHI The latest version also supports OPC UA, although I for myself had only used the older OPC DA components using DCOM up to now.

That was exactly what wanted to suggest, but missed to mention clearly. Thanks for jumping in. Yep, that is exactly what I do here. And be it just for clearness.

That only changes the perception of the problem, not its existence.

I have to disagree with that conclusion. Whenever I encounter a form with a tab control I consider breaking it up into the form with only the tab control (and the common controls around it) and have the different tab sheets extracted to individual frames. IMHO that is much easier to maintain than 1 form alone. Just imagine a group of developers each one working on one tab content. Given that breaking complex forms up into smaller parts reduces dependencies and is way better to maintain, I would never go and glue different forms together into one.

Currently there is no way to disable themes on a per control basis that I know of.

Result := ASource.Replace('\n', #10).Replace('\t', #9); Perhaps not the fastest approach, but pretty simple:.