Uwe Raabe

Project Magician follows a different scheme: It has an option to remove all child entries so that only the base values are effective. Unfortunately it doesn't force you to change base values only nor does it warn if you don't.

This can be easily solved by converting to string before calling the constructor: JSonObject.AddPair('Test', TJSONNumber.Create(High(UInt64).ToString)); // add System.SysUtils to uses clause If the UINT64 value is already correct in the JSON string it is properly converted to an UNIT64 later.

I'm sorry, but I have no clue what you are talking about.

I have to revert my statement: Currently not even creation of a UINT64 is supported. Nevertheless, the values are always stored as string, so no restrictions apply here. It is the responsibility of the developer to do the conversion needed. For completeness I suggest to create a QP request. Internally it needs just some extension to the case statement in TJSONString.AsTValue.

I guess you already did: https://quality.embarcadero.com/browse/RSP-33469

Probably not. Although it accepts UINT64 at creation, there is no support for retrieving it. I suggest to file a QP report.

Licenses are bound to the machine name, so you probably have to use your serial to register online on the new system. This should work for a certain (low) number of times after which you need to ask for a registration bump. If you have an active subscription you can contact support for that, otherwise you need to ask sales for a bump.

Unfortunately, changing any version information values at least once will break inheritance and the values in that build configuration have their own life. There is no built-in way to establish inheritance - unless the entries are removed from the dproj with some exterenal tool. That is the reason why Project Magician has this option

Can you elaborate on what do you expect instead?

And they are back again!

Not sure about your system, but when I here hover over your post there is a Report post label highlighted in the post title to the right, which can be used to, well, report the post.

Existing project is just a bit vague.

I would also recommend doing it in one step to the most recent version. Just make sure to disable all new features like VCL Styles or High DPI support (which is enabled by default). Using the IDE in highdpi:unaware mode may also simplify ones life in case one has a high dpi system for development.

I luckily managed to grab a copy in good condition (including CD) for unbelievable 12.38€ - sometimes it pays to have relatives in the U.S. Now I only have to wait for them visiting us in November, but looking at the ~65€ they tried to charge for shipping it to Germany that is definitely the better option.

That is not limited to frames, but affects forms and data modules, too. Looking for external links is done by component names - thus the first found wins. One could argue that this could be extended by inspecting the unit names available in the uses clause, but it is just the other way round: When the (wrong) component is found by name, the (wrong) unit name is automatically inserted when it is not available in the uses clause already. The designer part of the IDE is a mighty and sophisticated invention, but it has its limitations. What can be done is not nearly the same as what should be done.

Looks like as designed:

They are hard-coded.

At least recent versions of Delphi allow adding repositories located at arbitrary places. So if various computers have access to a common network share, you can use that for your templates. Alternatively one can manage these repositories and its templates with version control as with any other sources like f.i. common library code.

Alternatively create a new project and save it (best with decent file names). Then select Project - Add To Repository from the menu, select a proper place to add and type some nice names. After that you can select File - New - Customize to add the new entry to the favorites. As a gimmick you are directly asked for a target folder after selecting your project from the repository. Also, when all your VCL projects have a main TForm and a main TDatamodule and a separate TDatamodule with a TImageCollection, you can prepare that before adding the project to the repository (or create a separate entry for that) and you may save quite some more clicks and keystrokes.

Interesting. Just recently someone in the German forum claimed that as a welcomed feature here.

In 10.3 there is just no ImageName property in TToolButton either. ImageName support started with 10.4. In 11.3 there still is function TVirtualImageList.IsImageNameAvailable: Boolean;

In 10.4+ it is and versions before have no ImageName properties. function TVirtualImageList.IsImageNameAvailable: Boolean; begin Result := FImageNameAvailable; end; Actually that function is introduced in TCustomImageList. It is just overridden in TVirtualImageList.

You can as well override the IsImageNameAvailable function for that subclass and just return False.

The ImageName can only be stored when the linked image list supports it. A plain old TImageList does not, so that won't make any problems. The new TVirtualImageList introduces ImageName support, but makes it configurable with its ImageNameAvailable property. Setting that to False avoids setting the ImageName property on the linking controls. You might have to clear existing ImageName values manually, though.

... and the ability to simply move the database file from embedded to server and vice versa.