Uwe Raabe

I just realized that this is far more complex than I anticipated. The current implementation takes one or more lines and splits them each independently. If a line break is inserted, the remaining text is also handled as if it were independent. Unfortunately that will not work reliable when semantics come into play and some state has to be carried on. Seems I have to re-design the whole approach before it can be used in production.

Well, I am thankful for every test case. The test case should have: the complete line with leading spaces the expected length of the first line after wrapping the wrap margin to use (default = 80) the indent for the wrapped lines (default = 4)

Not something that I am aware of, but there are still areas in MMX which I am not very familiar with. MMX marks the project modified when the MMX settings dialog is closed with OK or Apply is clicked, but nothing of that happened in the video. The weird thing is that I made the test with MMX installed, too - and it did not happen. I do the same test with other projects and not one shows the always compile problem. Can you export the MMX registry key HKEY_CURRENT_USER\SOFTWARE\Raabe Software\MMX\15.0 and send it to me so I may track that down?

As that matches my test scenario pretty close, it may be caused by some differences in our environment. Which plugins do you have installed?

Just clear the entry for the Git exe in Tools - Options - Version Control - Git

Recently I noticed a freezing IDE while loading some source files. The actual cause was the internal Git client prompting for credentials in an invisible console window. Disabling that client fixed the problem.

A simple test doesn't show that behavior here. To eliminate the chance that the application is just too small to make that effect visible, I checked the timestamp of the exe. BTW, the exe is not even recreated when I switch projects inside the project group in between. Can you spot any changed files in the project folder that may be the cause for the effect you are seeing?

One of my customers switched from SVN, Bugzilla, ContinuaCI to Azure DevOps with Git repositories. Only ContinuaCI has been kept - mostly because the switch to Azure Pipelines would have been a too large step for one move. Depending on the range of support for Azure DevOps in the coming releases of ContinuaCI it may as well keep its place as the favored build system for a long time. The switch from SVN to Git was more a mental problem for the developers than a conversion one for the repositories. We made a clear cut in the history and split the monolithic repository in several smaller ones. Common libraries are handled as submodules. Bugzilla tickets were (and still are) moved to Azure DevOps with a self written tool (in Delphi of course). We also use a keep only what is needed approach here and archive the remaining Bugzilla data in a few months or so. The acceptance in the team after these changes is very positive. Things work much smoother as before and previously tedious tasks are either much easier or completely automated now.

Given some proper hardware working in a VM is not noticeably slower. (OK, I can only speak for VMware Workstation here)

Does this still hold true for Delphi 10.4.2? I cannot see any flaws with the auto-created manifest, but that might as well be due to my settings not covering the problematic areas.

Know bug: Duplicate VERSIONINFO resource using midaslib It only happens when you compile with Debug DCUs on. You can safely ignore that warning.

Indeed! Perhaps my advantage is that I had communicated with Matthias personally in German, so I never stumbled upon the name similarity.

The zip file containing the source also contains an AlgoSim.dpr, but the dproj is still missing. Thus the project cannot be compiled as some units are not found. Also the package projects for the design time components are missing, but a quick analysis revealed that all pas files are included.

What makes you think that? madExcept is from Matthias Rauen (aka madshi) and DebugEngine is from Mahdi Safsafi.

The documentation found in System.SysUtils.pas is pretty comprehensive. A thorough read is recommended. { The Format routine formats the argument list given by the Args parameter using the format string given by the Format parameter. Format strings contain two types of objects--plain characters and format specifiers. Plain characters are copied verbatim to the resulting string. Format specifiers fetch arguments from the argument list and apply formatting to them. Format specifiers have the following form: "%" [index ":"] ["-"] [width] ["." prec] type A format specifier begins with a % character. After the % come the following, in this order: - an optional argument index specifier, [index ":"] - an optional left-justification indicator, ["-"] - an optional width specifier, [width] - an optional precision specifier, ["." prec] - the conversion type character, type The following conversion characters are supported: d Decimal. The argument must be an integer value. The value is converted to a string of decimal digits. If the format string contains a precision specifier, it indicates that the resulting string must contain at least the specified number of digits; if the value has less digits, the resulting string is left-padded with zeros. u Unsigned decimal. Similar to 'd' but no sign is output. e Scientific. The argument must be a floating-point value. The value is converted to a string of the form "-d.ddd...E+ddd". The resulting string starts with a minus sign if the number is negative, and one digit always precedes the decimal point. The total number of digits in the resulting string (including the one before the decimal point) is given by the precision specifer in the format string--a default precision of 15 is assumed if no precision specifer is present. The "E" exponent character in the resulting string is always followed by a plus or minus sign and at least three digits. f Fixed. The argument must be a floating-point value. The value is converted to a string of the form "-ddd.ddd...". The resulting string starts with a minus sign if the number is negative. The number of digits after the decimal point is given by the precision specifier in the format string--a default of 2 decimal digits is assumed if no precision specifier is present. g General. The argument must be a floating-point value. The value is converted to the shortest possible decimal string using fixed or scientific format. The number of significant digits in the resulting string is given by the precision specifier in the format string--a default precision of 15 is assumed if no precision specifier is present. Trailing zeros are removed from the resulting string, and a decimal point appears only if necessary. The resulting string uses fixed point format if the number of digits to the left of the decimal point in the value is less than or equal to the specified precision, and if the value is greater than or equal to 0.00001. Otherwise the resulting string uses scientific format. n Number. The argument must be a floating-point value. The value is converted to a string of the form "-d,ddd,ddd.ddd...". The "n" format corresponds to the "f" format, except that the resulting string contains thousand separators. m Money. The argument must be a floating-point value. The value is converted to a string that represents a currency amount. The conversion is controlled by the CurrencyString, CurrencyFormat, NegCurrFormat, ThousandSeparator, DecimalSeparator, and CurrencyDecimals global variables, all of which are initialized from locale settings provided by the operating system. For example, Currency Format preferences can be set in the International section of the Windows Control Panel. If the format string contains a precision specifier, it overrides the value given by the CurrencyDecimals global variable. p Pointer. The argument must be a pointer value. The value is converted to a string of the form "XXXX:YYYY" where XXXX and YYYY are the segment and offset parts of the pointer expressed as four hexadecimal digits. s String. The argument must be a character, a string, or a PChar value. The string or character is inserted in place of the format specifier. The precision specifier, if present in the format string, specifies the maximum length of the resulting string. If the argument is a string that is longer than this maximum, the string is truncated. x Hexadecimal. The argument must be an integer value. The value is converted to a string of hexadecimal digits. If the format string contains a precision specifier, it indicates that the resulting string must contain at least the specified number of digits; if the value has less digits, the resulting string is left-padded with zeros. Conversion characters may be specified in upper case as well as in lower case--both produce the same results. For all floating-point formats, the actual characters used as decimal and thousand separators are obtained from the DecimalSeparator and ThousandSeparator global variables. Index, width, and precision specifiers can be specified directly using decimal digit string (for example "%10d"), or indirectly using an asterisk charcater (for example "%*.*f"). When using an asterisk, the next argument in the argument list (which must be an integer value) becomes the value that is actually used. For example "Format('%*.*f', [8, 2, 123.456])" is the same as "Format('%8.2f', [123.456])". A width specifier sets the minimum field width for a conversion. If the resulting string is shorter than the minimum field width, it is padded with blanks to increase the field width. The default is to right-justify the result by adding blanks in front of the value, but if the format specifier contains a left-justification indicator (a "-" character preceding the width specifier), the result is left-justified by adding blanks after the value. An index specifier sets the current argument list index to the specified value. The index of the first argument in the argument list is 0. Using index specifiers, it is possible to format the same argument multiple times. For example "Format('%d %d %0:d %d', [10, 20])" produces the string '10 20 10 20'. The Format function can be combined with other formatting functions. For example S := Format('Your total was %s on %s', [ FormatFloat('$#,##0.00;;zero', Total), FormatDateTime('mm/dd/yy', Date)]); which uses the FormatFloat and FormatDateTime functions to customize the format beyond what is possible with Format. Each of the string formatting routines that uses global variables for formatting (separators, decimals, date/time formats etc.), has an overloaded equivalent requiring a parameter of type TFormatSettings. This additional parameter provides the formatting information rather than the global variables. For more information see the notes at TFormatSettings. }

Please show your code - otherwise we all can just guess.

Regarding IDE themes I have given up trying to act 100% correct. As switching themes back and force is a rare process and the fact that the display is correct on the next IDE start led me to the decision to leave things as is for the moment.

Thanks, I will investigate your findings to track that down. The described behavior even bothers myself.

That was the story that I had in mind when writing my comment.

Make a photo with your smartphone

I just created a feature request.

AFAIK there is no such option. MMX parses the methods bodies and writes them in the requested order with a hard coded one line between each method body. Comments preceding each method are associated to that method (at least with the default parsing settings). The two empty lines after the method bodies in your example are not associated with the method.

DDevExtensions is open sourced, IDEFixPack is not.

Do you by any chance happen to have Project Magician installed with Auto LibSuffix option active?

In which build/platform configuration are you removing that value?