Uwe Raabe

This Editor is for TImageList, not for TVirtualImageList. AFAIK, the editor for TVirtualImageList is not shipped as source.

He already mentioned before: As I already own a license for HTML Components there is a good chance that it may be included as an extension to the Unit Dependency Analyzer in MMX.

Is there a way to setup a shortcut to "re-run" the Delphi LSP instances?

Seems you are still refusing to give the formatter settings you are using. How do you expect being helped if you don't give us the requested information?

Of course you can - just write it down. Note, that a style guide is not applied automatically. The developers must adhere to it when they write code. As we don't know what your are doing in the moment, we cannot say what you need to change to get the desired outcome. Therefore my request above.

I cannot reproduce that behavior here. Can you give detailed steps, please?

Can you show the complete code block with real indentation and your Line Break formatter options?

Are you asking a theoretical question or in the wrong forum?

It probably is part of the UniDAC components from DevArt.

I will try to reveal not too much, but I expect these questions to have satisfying answers with the release.

The line breaks in the code is always CR/LF as that is Windows standard, but you can define the line breaks that the compiler uses to make a string out of it. As string is always Unicode, there is nothing to define. Whatever you need the string for has to take care that it is converted to the correctly encoded byte sequence. It seems that quite some part of this discussion is missing the target. The feature is about line breaks inside string literals, which previously could only be created by concatenating strings and line breaks. The new syntax allows an easier way to write (and paste) with the benefit of better readability. And finally, if someone doesn't like it there is no obligation to use it.

Try setting FetchOptions.LiveWindowParanoic to True.

The voting system is to give priority to some issues over others. Priority may be different for all users here. It is counter productive to vote for an issue that has less priority to oneself, as that reduces the chance for issues you prioritize to be implemented.

Why not https://quality.embarcadero.com/browse/RSP-33115 ? That one already has 17 votes (which is not very much either and lies in the ranks at about 180)

Can you list the following settings for the TFDTable instance: CachedUpdates FetchOptions.Unidirectional FetchOptions.CursorKind FetchOptions.LiveWindowParanoic Also, is KeyIdx a primary or unique key?

I have difficulties to understand your intention here. Why would you want to enter a multiline string literal to declare a single line string literal? The whole purpose of the new multiline string literal is to get line breaks into a string literal. There is no need to have line breaks when they are later ignored anyway.

There already exists a syntax to achieve this: const blub = 'Lorem' + ' ipsum' + ' dolor';

That is exactly my own experience with MMX. When I took over the project it already was way behind the current language and it needs quite some time to catch up. While that may be possible for the IDE itself, as the owner has at least some control over the release date, this fails completely for 3rd party tools even if their maintainers participate in the beta (at least everyone willing can opt for that). A lot of enhancements are not ready early in the beta and often changed in between due to the ongoing discussion. Usually there is only a small time left before release where a feature is stable enough to support it in ones tool. Unfortunately the effort to design and implement that while staying compatible with older Delphi versions needs way more time as is left.

@dummzeuch I haven't had a look at it for quite some time, but is the formatter free/open source or are there any restrictions to it?

BTW, I like the fact that it is the closing quotes instead of the starting one. Imagine you need to adjust the indentation of the whole literal just because you decide to change the name from blub to something with not the same length.

What if you want a line with a single semi-colon inside the string literal? With the current implementation your example would be written this way: blub := ''' line1 line2, indented 3 spaces line3 '''; // the ending triple quotes are aligned with the no-indentation position Some background for this discussion: Raw string literal

If the parser is too complicated by itself, it probably doesn't matter which syntax change is actually chosen.

The docs that comes with the beta installer. You don't expect beta testers to discover how to use new features by blind guesses, do you? Of course, one has to participate in the beta to get access to both, but everyone with an active subscription can ask for it.

The docs contain more information than the blog post shows.

Exactly! Nobody is forced to use this new feature. Also, I don't see anything breaking except tools parsing new code using that feature. Obviously that is always the case with new language features. The only way to avoid that is not allowing new language features in the first place.