Uwe Raabe

As I cannot spot one, do you happen to have a QP report at hand? Otherwise I will create one. It would be nice if you can post the source here, unless you opt for creating that QP entry yourself.

Currently this is not implemented. The context is populated with help from the IDE ToolsAPI, which is not available for a command line tool. While in principle this is possible by evaluating the dproj file, but currently I have no spare capacity for that. When time allows I can share some code that can serve as a start.

Indeed

type TObjectDictionaryWithDuplicateObjects<K,V:class> = class(TObjectDictionary<K, TObjectList<V>>) public procedure AddObject(const Key: K; Value: V); end; procedure TObjectDictionaryWithDuplicateObjects<K, V>.AddObject(const Key: K; Value: V); var list: TObjectList<V>; begin if not TryGetValue(Key, list) then begin list := TObjectList<V>.Create; Add(Key, list); end; list.Add(Value); end;

That is exactly what I would have suggested. I have seen quite a couple of implementations using that pattern.

Actually one need to enter just MYDEF, just like you do for the Defines in the compiler options or the options of the Unit Dependency Analyzer. BUT, there is a refresh problem in the current MMX version: You have to restart the IDE to make the MMX parser reload the defines. Of course that is quite buggy, as even switching the project misses to update the defines for the parser. I will fix that with the next version.

No. AFAIK it uses (besides some Windows core DLLs of course) only RLink32.dll and perhaps borlandmm.dll.

As it replaces dcc32280.dll and dcc64280.dll, which are used by DelphiLSP, the command line compilers stay the same and are not be affected.

Have you actually tried to specify DCC_UnitSearchPath on the MSBuild command? msbuild /property:DCC_UnitSearchPath="d:\mycomp\lib" myproj.dproj

It is possible that you have to implement it yourself in the way it is needed as it is noted in the docs: That said, giving a concrete example is difficult without knowing more details.

This code should terminate the application after the form creation without making the main form visible: Application.ShowMainForm := False; Application.Terminate;

Duh 🤯

The calls to SplitString look as if the parameters need to be switched. First parameter is expected to be the string to be split, while second is the string with the separators. Note that the QuickReport implementation allows only a Char for the separator, while the StrUtils one allows multiple separators.

Seems like the machine manufacture prefer the replace option. Sometimes they provide a replacement of the controller hardware, but often that turns out incompatible to the machine equipment. I would love that to be different, as it would allow me to sell updates to newer versions of my software developed with more recent Delphi versions.

Can you show both uses clauses of that unit?

Put the StrUtils into the uses of the implementation section or at least after QrCtrls.

My customer base has machines running even with Windows 95. It is quite common that such kind of machines are not able to get a new version anymore.

In that case you need to show more of your code.

LeftStr and RighStr are functions declared in StrUtils.

Which seems to be a no brainer since we just learned that you can just copy that code from Microsoft.

I doubt that:

That was exactly my thought. 👍

Have you tried using the debugger to inspect the actual content of Str in the problematic case?

Can you check what the IDE environment variable $(BDSCOMMONDIR) contains?