Uwe Raabe

Just curious: Do you know why wuppdi is mentioned in %ProgramFiles(x86)%\Embarcadero\Studio\21.0\Welcomepage\js\wpLoader.js var classHide = 'wuppdi'; var regHide = /\s*wuppdi/;

Workaround: Edit %APPDATA%\Embarcadero\BDS\21.0\wuppdiwp.ini and set sidebarwidth=200

There are probably still a couple of bug fixes and lots of performance improvements to be done. Until then new features are lower priority.

No problem: HKEY_CURRENT_USER\Software\Raabe Software\MMX\14.0

Known problem. Current workaround is to temporarily rename your v14 registry key, so that v15 will not see it.

Have you actually saved the changed layout?

I once wrote a tool for that: https://uweraabe.kilnhg.com/Code/Community/Delphi/CompressPath

The new PngComponents version 1.6.0 with Delphi 10.4 Sydney support is available on GitHub: https://github.com/UweRaabe/PngComponents While the version delivered with GetIt is still on 1.4.0, the above version f.i. supports the new feature of linking to a TPngImageList by ImageName in addition to ImageIndex.

There is an option (checkbox) that the theme follows the Windows theme. Try to switch that off.

The license text inside ELC stays the same. The list in License Manager after importing the new slip file should show 10.4 Sydney.

MMX version 15.0.15 now supports Delphi 10.4 Sydney.

By magnitudes

Open the ELC web interface and go to License Hosting. Enter your credentials and the certificate as given by Embarcadero. Click Host Licenses. Select the proper license and again click Host Licenses. Got to Licenses. Click on License Files and download the slip files (zipped). Extract the named license slip file. On each installation open License Manager and import that slip file.

You should be aware that assigning to TPicture.Graphic will create an internal copy of the source (see TPicture.SetGraphic), so you get a memory leak with the above code. As TPicture.Assign also uses SetGraphic internally, the above ist still valid for that one. Not refreshing the display may have a different cause.

Right. You only need to contact the Embarcadero Server when you register your Network License with your ELC instance and when this license get updated while your are on Update Subscription. I am not sure if I understand you here. As I said above: you need to register your Network License once when you enter it into your ELC Server instance. You also need to update this License whenever a new Delphi version is released and your license is still under Update Subscription. Without any Update Subscription the Network License stays valid inside your ELC Server. What do you mean with renew license of older versions? I still don't get the meaning of this term. AFAIK, any valid Delphi license up to a recent version also covers all previous versions down to Delphi 2007. At least my own licenses do. I also don't get the IP address issue. The ELC server is not bound to any IP address. Only the server name must rename the same. That is similar to the normal Named Workstation license, which is also bound to the computer name. I haven't been in the need to try, but it should be possible to re-install the ELC Server with the given login credentials and certificate number (optional) as long as the server name matches the previous one. I can't help and I don't mean to insult, but your arguments feel like just trying to forcibly construct a broken system where nothing is broken in the first place.

That is not true! Installations are not limited. The restriction is that you can run multiple instances of the same IDE version (10.2 and 10.3 are different versions) on up to three different machines at the same time. That is you can run Delphi 10.3 on the same machine (as many as it can cope with) and still start Delphi 10..3 on two more VMs or physical machines, where each can run multiple instances. Together with that you can run Delphi 10.2 instances on up to three different machines, be it the a same as above or others. You just have to make sure that all these machines can connect to the ELC Server and you are logged in at these machines with the same user name the license is bound to (you can change that yourself in the ELC Server). My installations are spread over dozens of VMs and I never reached that 3-instance-limit.

Not sure how you do, but I have always just copy the Delphi 7 license data to another machine without any further registration. Actually I guess that Delphi 7 is not even covered by the ELC server - it is just way too old. At least you should still have the original CD, so no need to download. Also, I am not sure what the term renew their licences actually means in this context. Is this just registering a license or is it bumping the registration count? It is not even clear what Marco is saying to be taken away from former customers. He just says you lose access or download options. Well, he will have a hard timer to stop you to access your Delphi installation on your system. And again, move your Delphi installation into a VM and take care of backups. No need to install again, no need to register again and no need to bump your registration count. Perhaps you should tell your customers to do the same. BTW, I wonder how many software companies still provide installation files for like 20+ years old software - at no cost. (most of those companies probably don't even exist any more)

That is not what can be read in that comment. I cannot see anything about licenses being invalidated or not being able to compile old code. Even the question does not imply that. It is only about downloading the setup files, isn't it? If my business were founded on the fact to be able to download old Delphi installation files I would do something wrong in the first place. I suggest to install old Delphi versions inside a VM and have a good backup strategy for those - like many people I know are already doing for years now. In case someone is worried about not being able to register a valid license later, the solution can be to convert the Named User license into a Network Named User license. That requires an ELC server installed somewhere in the local network, but it simplifies registrations a lot. License bumps are no longer necessary with that. Moving a Delphi installation to a new machine boils down to installing it and importing a slip file. My own situation covers quite some of your points. I have old software that has to be maintained (if at all) with old Delphi versions. Some of my customers are stuck with an old Delphi version, so I am regarding their projects. I see no problems in any of those. Even if Embarcadero would be hit by a comet, I would be able to work for plenty of years. No! If anyone would be affected there are ways to prepare for it and be safe. No problem and I think it is fair. There is plenty of other software where it is impossible to get old installation files now. I can still remember times when software was delivered in CD or even Floppy disks. We were used to make backup copies of those in case they will break and the vendor would charge for a replacement CD - if even offering that at all. One can do something similar for ISO images. Having that said, the other points are just meaningless.

You can also check the dproj file the DesignClass and FormType values to be correct. <DCCReference Include="Unit527.pas"> <Form>DataModule527</Form> <FormType>dfm</FormType> <DesignClass>TDataModule</DesignClass> </DCCReference>

I guess David is referring another assembler sequence.

The maintenance confirmation mail and the support terms say: There is a difference between the Primary Contact (the one who pays the bill) and Authorized Contacts (the developers using the product). So tell the person in charge in your company to assign you as an Authorized Contact.

For Windows 8+ there is InterlockedCompareExchange128

Yes, because the reference to tPolar2D is only inside tPoint2D, which still has to be declared after tPolar2D. The benefit of the operators is the ease of conversion by assignment. This is the (corrected) declaration with some example assignments (TBD: calculations): type tPolar2D = record Radius: Double; azimuth: Double; end; type tPoint2D = record x: Double; y: Double; public class operator Implicit(A: tPoint2D): tPolar2d; overload; class operator Implicit(A: tPolar2D): tPoint2D; overload; end; class operator tPoint2D.Implicit(A: tPoint2D): tPolar2d; begin Result.Radius := ... Result.azimuth := ... end; class operator tPoint2D.Implicit(A: tPolar2D): tPoint2D; begin Result.x := ... Result.y := ... end; var cart: tPoint2D; pol: tPolar2D; begin cart := pol; pol := cart; end.

What about operators: tPoint2D = record x: Double; y: Double; class function Implicit(A: tPoint2D): tPolar2d; class function Implicit(A: tPolar2D): tPoint2D; end;

I can't help, but this looks like you are trying to make that dictionary construct work like a database.