Uwe Raabe

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?

Some information about App Tethering: Using App Tethering

The question is now: What is an individual company roadmap session (in contrast to a plain old roadmap)?

Try HWND_BROADCAST instead of Application.Handle

The TVirtualImageList can only hold images of one size, which it retrieves from a TImageCollection. That works even if the requested size is not available in the collection. In that case one image is scaled to the requested size. To have multiple sizes simultaneously you need separate TVirtualImageList instances. If you need only one size, just set the TVirtualImageList to that size.

It has been for a long time that selected beta testers (like f.i. all MVPs and Tech Partners) are invited early to a beta cycle, while users with an active (normal) Update Subscription are invited at a later stage (so they actually are already open to any willing subscriber). Now it seems that having a Premium Update Subscription puts you into the first group, too. Does not look like a big change to the previous system to me. May be they want to put more value into the Premium part, which isn't a bad thing. Nothing is taken away from anyone.

Sorry. Perhaps I misunderstood as I was under the impression that this was the cause of your problem.

That doesn't surprise me, as it probably does the same as the new IDE functionality does. Would it be possible to get hands on such a file with a single CR for testing purposes?