Leaderboard

No more C++ Builder crashes at debugging.

Thank you to everyone who provided suggestions! I have a working prototype that provides the desired functionality. I created a custom control (TSizeableLabel derived from TCustomControl) that "wraps" a TLabel. The TLabel is passed as an argument to TSizeableLabel's constructor and TSizeableLabel makes itself the parent of the label. It also makes it's size just a little bit bigger than the size of the label. The extra size is to accommodate the 8 size handles that are drawn to enable resizing. I'm planning to put my prototype in a public github repo soon.

Some of my stuff is in the QA portal (menu fixes I think) and I still have to use it despite the reports being marked "fixed." But most of my workarounds are done on-the-fly with my own inherited form and frame classes and would be too much bother for me to pull out to show anybody. I guess if I were to share a "feel" for how it's going, I'd say it's getting better. I think Embarcadero should force their developers to use their own IDE in a mixed-DPI environment in various configurations and not stop fixing scaling issues until they can do everything seamlessly. Who knows, maybe they already have, and they just aren't exposing the problems I run into.

I can imagine that is the case. From (my sketchy) memory, I think I did investigate moving from an older VM, but in the end I started a new one. I tend to have as little installed on the VM as possible, so it wasn't difficult to bring one "up to speed" I have a Macbook Pro with an M1 Max, running a Windows 11 Arm VM (one with Delphi 12.2 and one with Delphi 11.3) using Parallels 20.1.1

Not sure who Dave is.... Delphi doesn't know that the type of the thing to the right of the equality operator is an array, it thinks it is a set. That's why you get the error. You might not like this, but this is just how it is right now. From the language perspective, there is clearly some magic disambiguation applied in the case of the assignment operator that isn't applied elsewhere. As Remy says, all you can do is to open a ticket. Shooting the messenger isn't going to get you anywhere. But even if the code did compile, what would you want it to do? For dynamic arrays, like other reference types, the equality operator = means reference equality. But I suspect that you would want value equality. So even if this code ever compiled, I don't think it would do what you want to do. In which case you will need to implement a method or function to perform value equality testing, and so the topic becomes somewhat moot.