71–76 of 76 posts
Aside, I have used this in the past for GUI on windows and it was amazing. Like .NET but native and better.
Earlier quoted context omitted.
This kind of email+phone registration was common in the 90s and earlier. Oh, wait, it's 2023.
It is perfectly common in 2023 for the kind of clients that usually pay for development software tools.
Earlier quoted context omitted.
It took Microsoft some generations to stoppe requiring you to sign-in to use community edition after the trial period ends. Perhaps Borland will fix this in some years as well.
Far as I can tell, it still does. Nothing more annoying when chasing a bug than being forced to look up a password I haven't used for several months in order to use the debugger.
Earlier quoted context omitted.
Whatever you say.
...is correct. Visual C++ has a visual resource editor, but this isn't what C++ Builder does. C++ Builder edits live objects, you declare a class with its properties (this needs extensions to the C++ language) and during design time the object is instantiated and edited visually through the property editor ("object inspector"). This works for both visual (buttons, controls, etc) and non-visual objects. The difference…
Earlier quoted context omitted.
This is also baffling. A button, a text input, a checkbox, a drop list, a combo - they all have a "default" look in every Windows version since 2.0 (1 didn't have the drop list, IIRC). It shouldn't be difficult to make an abstract description of a dialog box look at home with a new version of the OS and, yet, digging through Windows 10's built-in apps you sometimes find things that you recognize as skinned versions o…
The Office team used to pioneer (hard-code) the look and feel for the UI, and then the Windows team goes and implement the look and feel system wide in a generic way. Then somewhere along the way, the Windows team decided to hard-code the look and feel that you could now do an archeological dig through decades of UI.