Uwe Raabe

Yes. The command line application is named MMT_UDA. It expects at least the file name of the dependency project (.mmdep) and the report type (-uses, -cycles or -ldp). For LDP reports the output file name is taken from the .mmdep, but for other reports you must specify that name as a third parameter.

I have no CE, but it works in Enterprise.

Here you can lookup the Linus requirements: http://docwiki.embarcadero.com/ELC/53/en/Installing_AppWave_Enterprise_License_Center#Linux.C2.AE_Requirements

I guess it is meant for different VMs using the same Windows license.

AFAIK is the IDE license bound to the machine name only. I often move Delphi VMs to other drives without any problems. There must have happened something inside the VM to trigger this.

8 hours ago, Joseph MItzen said:

1200 Euros for three days? That's more than my desktop computer cost.

Well, it is only a fraction of the cost for my next one.

Can't you habe empty components for both types that you can refer to?

The colon in the time zone offset seems to be optional, while the Delphi implementation requires it. I suggest creating a QP entry with a test case showing the problem. A failing test case often increases the probability for a quick fix.

Can you provide a minimal example showing the problem?

You can create the instance on first use and then reuse it when needed.

15 minutes ago, wpcubed said:

What I miss on the linked page is a downloadable ZIP with the necessary files in. 

The first line of the paragraph The Application contains a download link.

Doesn't the control already has the focus during the OnClick event? In that case a WM_SETFOCUS message might not be sent.

6 hours ago, Joseph MItzen said:

it struck  me as strange that not even the project manager had any idea when the product would be released.

I am pretty sure he definitely had an idea, but then things were going to change a bit. Let's see the positive side: Embarcadero obviously has some sort of agile culture.

28 minutes ago, Yaron said:

And if it's not just around the corner then my subscription might end and I'll be stuck with a beta version.

Well, then simply renew your subscription and you are good.

 I often have different optset files containing unit search path entries. Usually I separate them by library name.

F.i. there is one optset for TMS Scripter or GLScene, where several folders have to be added to the search path. As my folder layout for projects is consistent, the search path for each library is the same for each project. Thus I only have to add that optset to each project (only the first one, the others with drag'n'drop) to add the necessary folders to the project search path. As a gimmick I can see immediately which libraries a project depends on.

This is als pretty convenient when the projects inside a project group share a couple of local folders in their search path. Using an optset for that makes changing the search path for all projects at once just a breeze.

Unfortunately FinalBuilder is not able to resolve those optset references. Therefore I have written a small program doing that, which is called immediately before the compile action.

Regarding RSP-14723: Indeed, optset references are not removed from the dproj. As that is not very common in my workflow I usually fix this by editing the dproj manually.

1 hour ago, PeterPanettone said:

Why are there no Win64 compiler versions listed

Basically because there has been no need to implement it yet.

The compiler version merely sets the default conditional defines (like VER320) related to the compiler, but those can be extended by yourself in that same dialog. Also, only the uses clauses are parsed for dependencies, so most of the code is ignored anyway. 

What differences in the dependency results do you get with the plain Win32 compiler setting compared to Win64?

Another advantage of actions and action lists is that they can reside on a datamodule, which can be used in a VCL and a FMX application. Thus the same action logic can be used, which might have to be duplicated otherwise.

If it is related to TCustomEdit executes VK_DELETE while observer forbids it should be fixed in 10.3.2

Selective Debugging allows to select the debug DCUs on a per unit basis. This doesn't affect the content of the call stack.

Honestly, I doubt that removing this information from the call stack is of any benefit at all. In fact it would camouflage the actual program flow rendering the call stack next to useless.

I often get the impression that our computers already established some form of artificial intelligence, but for some unknown reason it usually turns out to be a mean one.

Perhaps that big company is run by the fathers of those Tom, Dick an Harry and they trust their kids more than the experts?

Is this VCL or FMX? Which target platform? Can you provide a minimal example showing that?

5 hours ago, dummzeuch said:

Unfortunately it supports only Delphi 2010 and later.

I actually rate this as an advantage. Otherwise it would not be much different to the old DUnit.

10 minutes ago, A.M. Hoornweg said:

Does this support copying to the clipboard?  In Delphi XE it doesn't.

I am not sure if the quote is actually the intended one, as Thomas description is not related to the clipboard at all.

In case you are referring to the MMX solution, make sure that you copy the interface (not its methods) from the contents list of the MMX Code Explorer window and paste it into the members list of the target class.

You may also have a look into CodeSite, which allows similar things in a more convenient way. The Express version can be installed via GetIt,