PeterPanettone

Thanks also to everybody for helping!

Thanks, Uwe, this is a VERY GOOD idea! In fact, this completely solves the problem with pasting many raw use-clause-items. Didn't even know Multipaste before. Maybe it should be called SmartPaste instead of MultiPaste, as it really is not a multiple paste action. Maybe also the dialog should automatically remember its last settings.

I could easily write a small script-tool which fixes the commas. But at a more general scope, it would be interesting if it was possible to fix these syntax errors with the help of the compiler?

They come from an external source by pasting.

There would be many lines. An automatism would be faster than adding the commas manually. Ideally, I would select a block of code and the errors in this block would be fixed. Ideally, the compiler would help.

In the video, it fixes just one error at a time. Can it also fix multiple errors with one action? But I doubt it can fix Delphi syntax errors... or is it configurable?

For now, yes.

Is there a specific technical reason why FreePascal can do it and Delphi can't do it?

So why Embarcadero hasn't fixed these bugs in 10.3.1?

Well, if Editor marks inline variables as error is the only bug caused by inline variables then I can easily live with it as I have switched Error insight off: Or are there any other bugs caused by inline variables?

Is there somewhere a comprehensive list of bugs provoked by inline variables?

😞 😞 😞

Thanks, Stefan. I would have preferred "the old way" which is more formal. BTW, are there any drawbacks in using inline variables? I am not sure, but I remember having read somewhere that there is still a bug in using inline variables.

The Delphi IDE has a "Lock Toolbar" popup menu option: However, even when this option is activated then the MMX toolbars are still movable: Wouldn't it be better if the MMX toolbars would be locked too in this case?

Just for whom may be interested: The CnWizards Lock Toolbars setting is located here: HKEY_CURRENT_USER\Software\CnPack\CnWizards\CnPaletteEnhanceWizard -> LockToolbar

Please file a Quality report: https://quality.embarcadero.com/

Good! I don't think that reading this setting would be extremely difficult. But many users do use the very popular CNWIZARDS. That would be a design decision. Easy: In this case, the default setting (not locked) would come into effect. Probably yes.

Some people are addicted to traditional tools. For example, I love my old breakfast mug and wouldn't use another one.

Well, it has been confirmed now that the "Lock Toolbars" setting is from CNWIZARDS and not from the native Delphi IDE. Since the Delphi IDE seems to have no native setting to lock the toolbars (which is a standard feature in most professional toolbar applications) I would suggest that MMX reads this setting from CNWIZARDS and locks/unlocks its toolbars accordingly. What do you think?

I have filed a new feature request in the GExperts ticket-list: #58 List of all uses clause items in the whole project Please create a GExperts expert to create a merged list of all uses clause items in the whole project without duplicates. EXAMPLE: Project1 contains Unit1 and Unit2. Unit1 interface uses clause contains: Vcl.Forms, Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, System.Actions, System.ImageList, hyieutils; Unit1 implementation uses clause contains: Vcl.Graphics, Vcl.Controls; Unit2 interface uses clause contains: Vcl.Forms, Vcl.Dialogs, Vcl.ExtCtrls, Vcl.ActnList, Vcl.ImgList; Unit2 implementation uses clause contains: hyieutils, iesettings, iexRulers; The list created by the expert would then look like this: Vcl.Forms, Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, System.Actions, System.ImageList, Vcl.Graphics, Vcl.Controls, Vcl.Dialogs, Vcl.ExtCtrls, Vcl.ActnList, Vcl.ImgList, hyieutils, iesettings, iexRulers; Of course, it should be possible to copy the list to the clipboard, save it as text, etc.

Thanks.

I am not sure what you mean.

And how do I know that the name of this toolbar is "Navigation Toolbar"? This makes me think of the German fairytale "Rumpelstilzchen": "Oh wie gut, dass niemand weiß, dass ich Navigation Toolbar heiß!"

BTW, the caption "Lock Toolbar" is misleading. It should be "Lock Toolbars" instead because it affects all IDE toolbars.

Uwe, thank you very much, this was so annoying! But this IMO is also a good example of a bad user interface. Imagine this situation: To turn on/off the light in the living room you would have to go to the bathroom because the light switch for the living room is in the bathroom. Obviously, the better solution would be to have the light switch for the living room directly in the living room!