3 ms·
And then MS came up with MFC which was slightly better. But only slightly. Borland had a better solution if I remember, in their C++ Builder thing. Another "a
by raverbashing 12y ago
And then MS came up with MFC which was slightly better. But only slightly.
Borland had a better solution if I remember, in their C++ Builder thing.
Another "adventure" I had in Win32, trying to make a dynamic dialog box (basically, selecting something in a list opened up a list of properties - like the Preferences dialog box in most browsers). It was some time before I figured out how to do it (there was a coordinate conversion needed)
- bhouston 12y agoBorland has OWL: http://en.wikipedia.org/wiki/Object_Windows_Library http://en.wikipedia.org/wiki/Object_Windows_Library Strangely it is still maintained by volunteers: http://sourceforge.net/projects/owlnext/ http://sourceforge.net/projects/owlnext/ But it was always behind Microsoft's MFC in terms of features. And you had to drop out of it for advanced stuff and then you had to spend a bunch of time figuring out how it actually worked.
- stormbrew 12y ago> And you had to drop out of it for advanced stuff and then you had to spend a bunch of time figuring out how it actually worked. This was really no less true of MFC, and imo the OWL code was a lot cleaner and easier to understand. In the end, though, they were both just wrappers around the windows api. But the GP seems to be referring to VCL, which is what came with Delphi/C++Builder. One of the reasons OWL was usually behind MFC was that Borland basically abandoned it and their mainline compiler products for the Delphi line, and C++Builder was always a second-rate product behind Delphi as well.
- raverbashing 12y agoYep, VCL not OWL As per Wikipedia "Much of the .NET design, especially WinForms, is modeled after the VCL."
- geoelectric 12y agoMFC was much more of a thin wrapper than OWL was, IIRC. Microsoft concentrated on bringing MVC-enabling classes for application development, and otherwise just basically wrapped the raw Windows API, whereas Borland actually created an honest-to-gosh object library to represent the GUI (and to an extent, provide a migration path from TurboVision, their DOS GUI library). VCL was even thicker still, having come from Delphi's rather successful attempt to duplicate the Visual Basic VBX components in a highly-extensible and more native way. Like you hint at, it was kind of a weird fit for C++Builder, since Object Pascal had somewhat different capabilities that they had to lay into CB making it a little bit of a bastardized spinoff of C/C++. .NET/C# was ultimately what came out of that heritage, after MS poached Delphi's architect. I think it benefited from not claiming to be C++.
- pjmlp 12y agoI read a story somewhere that MFC was originally much like OWL, but when Microsoft gave it to their test groups they found it too OO was thus MFC as thin layer was born. The Afx prefix comes from this library.
- userbinator 12y agoIt was some time before I figured out how to do it (there was a coordinate conversion needed) That sounds overly complex - all you need to do is to catch the listbox selection message, hide all the controls that shouldn't be shown with the current list selection, and show all the ones that should be. I don't see how a coordinate conversion would be needed for that.
- raverbashing 12y agoI don't remember all the details, but it was more or less like this (with MFC) I built the dialog using their tools, one for each "tab" Then I attached that dialog on the space for it based on the selection, and the coordinate transformation (was a function in MFC) Something like this http://stackoverflow.com/questions/2653130/how-to-get-size-and-location-of-a-control-placed-on-a-dialog-in-mfc http://stackoverflow.com/questions/2653130/how-to-get-size-a... Hiding/showing might have been a good idea, but for more complex dialogs it wouldn't work