Uwe Raabe

IIRC, Embarcadero Germany offers a 30% for discount Enterprise until the end of November, too. It wouldn't hurt to ask.

Because "Upgrade" means entering another serial number to upgrade f.i. from Professional to Enterprise.

I am not sure about the ISO installer, but the Web Installer also removes Rio before installing the new version. At least it asks you to confirm before doing so. Perhaps the ISO installer requires you to do that manually.

So, when did you get that serial number and when did install the CE with that serial number for the first time? IIRC, all CE serial numbers are only valid for one year.

AFAIK the CE will always be the latest available release. So if you get a brand new CE today you should get 10.3.3 - at least that is what the Feature Matrix suggests.

At the end it boils down to the question: Does it work for me or does it not? The answer obviously depends on the one who asks. That's why I am not going to suggest the formatter for everyone. On the other hand, just because it doesn't work for some people doesn't mean that I have to use another tool for myself, too.

As I said, it heavily depends on the coding style. I would never do this. The last time I wrote this kind of stuff was about Turbo Pascal 4 or so. I would declare explicit types for these records. Even if they are only used locally.

I am working with the integrated formatter without significant problems. Perhaps my coding style fits better than others. For those cases where the results are not to my liking I have found some workarounds, Nevertheless, I would prefer when Embarcadero would deliver the sources for the formatter. There is always room for improvement.

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.

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.

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.

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.

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.

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.