Uwe Raabe

An event is always declared as procedure(...) of object, which carry an invisible self parameter. This allows object methods, but excludes global procedure(...) and reference to procedure(...) declarations as well as anonymous methods, because they all lack that self parameter.

Especially as one cannot override virtual methods in a class helper.

Well, I don't see that flicker, but there definitely is a significant delay before the dialog opens. The flickering can be related to the actual form content that has to be loaded, so it might differ between projects.

Perhaps Add to Repository needs to open all pas and dfm files of the project first. That is backed by the observation that closing that project after that needs significantly more time than usual.

Indeed - and DelphiStyles has shown to be a competent and reliable partner for that. Highly recommended!

Why don't you just try the evaluation version?

Ini files lack proper structure support and MMX settings rely heavily on structure. For the purpose of your main question XML files would do pretty well - and not easy to edit is seen more as a feature here.

I actually think the same! Unfortunately it cannot be changed that easy. There are several places with registry access which have to be taken care of. Even the splitting in MMX and Shared, which have their roots in the common code between ModelMaker and ModelMaker Code Explorer, are a bit clumsy. Also it will not going to be an INI file because of the hierarchical structure of the settings tree. I will probably choose XML. Don't expect that soon, though.

For the adventurous of you there is a new download for a MMX Beta version: MMX Beta Setup (current build is 2287) You won't find many new features. The main work was removing unneeded stuff, making use of things not available in older Delphi versions and reorganizing the code. So be prepared to find areas where I accidentally broke something. I would appreciate if you send bugs as email to support@mmx-delphi.de - that way they are automatically added to the bugtracker and are less likely to be forgotten. Feel free to also discuss them here, but even then send that email, so I don't have to duplicate it by hand. Currently there is only one new feature: The MMX Project Options settings have a new check box "Auto Format". If this is checked MMX will execute a format uses clause command every time it adds a new unit to the uses clause. Obviously this only works when the Group and sort uses option is enabled in the Sorting section. Unless something prohibits me to do so, I will announce new builds in this thread.

Funny thing is that those toolbars are originally meant for beginners. Long time users usually prefer working with keyboard shortcuts. Also f.i. filtering members by kind and visibility with the filter buttons is probably easier and faster than using the context menu. It may be pretty hard to find a balance between scaring some new user with too much possibilities and boring them with too little. I am not sure whether I prefer to answer the question "How can I hide that?" or perhaps never being asked "Can it do this or that?". There are quite a number of people saying they cannot work without MMX (me included) after working with it for a while. I know there are others who never get beyond this point. They either will miss something or MMX is not the right tool for them. You cannot please everyone.

Noted!

Well, that can be taken care of. When the amount is reached and the icons are ready I can ask the designer to split the bill into a commercial and a private part. For the commercial part my commercial ego can provide invoices to the companies requesting one. Thus the cost will balance out the revenue on my side. Of course this also holds true for single person shops (I just figured out that the term One-Man-Shop is probably not gender neutral). My initial idea was to find a single sponsor to take care of the complete cost and thus can be billed directly, but the number of icons and thus the total amount turned out to be a bit more than I expected.

That is why I am trying to outsource the icons work. There is enough other stuff to do, that can only be done by myself. Start typing in the Search field in the Member Search bar. Not sure what you mean. All buttons show have their counterpart in the context menu. You can even hide all toolbars and work with the context menu alone.

I guess that is not feasible. I cannot foresee when I will have time to work on MMX and what I am going to target when I have.

I have good hope that this forum will suite us well when it is matured a bit.

Yes, that is what I was expecting when reading this topic title. The Fluid portal best suites my way of using this forum. I can quickly spot the topics with new content, although I would prefer that a click on that topic will directly locate that new content (I often miss that little symbol in front of the title I should use for that). When I need to concentrate on a specific sub group (like MMX) or go back I can just check/uncheck that in the list.

TLinkLabel is a wrapper around the Windows SysLink control. It has greater flexibility (f.i. can show a mixture of text and several links, not only one URL, as well as distinguish between a link, a focused link and a visited link) and thus requires a more sophisticated event handling (not every link needs to be opened in a browser). Anyway, my quote was rather related to the list of PITAs than your actual code.

Ignored topics are still visible in the Fluid list on the homepage.

Not really since TLinkLabel was introduced as a standard VCL control in Delphi XE2.

Without cross-checking the actual sources to make sure: If you enable Pre-parse Project Files and Persistent Module Information, it should be sufficient to open the relevant projects once to get the necessary information. Currently there is no way to specify some directories to scan as that is most likely a per-project setting. As MMX just recently added some per-project settings stored in the dproj file, there is a good chance for such a feature to be implemented in the future.

Looks like TMS AdvCardList might suite well: https://www.tmssoftware.com/site/advcardlist.asp

You can as well combine both avoiding the hide effect: TBar = class(TFoo) procedure Terminate; reintroduce; overload; end;

"The Dialog" in this context is the whole Project Options dialog - not only this special part of it about Runtime Packages. That is even exactly what David describes in his article.

There are already a couple of issues regarding these controls in the title bar. I suggest to add this to QP so it can be fixed together with the other ones.

David Millington explains in his blog post New in RAD Studio 10.3: Options Dialog Improvements in the section Dialog Search.