Re:"MFC programming", what the heck?
on
Qt vs MFC
·
· Score: 1
Strange I dont encounter this that much in the posix world, which runs everywhere, atleast not within the sae library/API.
I rather suspect their mess comes from the fact that they have to keep binary compability. And that MFC mostly a wrapper a round the Win32 API, to which they change their internals with virtually every build(or so it seems). Its though a pretty bad excuse, the thing is to do it right from the beginning.
Re:wxWindows comparison...
on
Qt vs MFC
·
· Score: 1
ohh. Someone a while ago told me about wxWindows.
So ahead I went an tried to make my first small test app. During that hour I decided that wxWindows is crap. While abit better than MFC, theres much of the same. And i truly dislikes MFC.
"MFC programming", what the heck?
on
Qt vs MFC
·
· Score: 2, Insightful
I've been doing lots of Qt, GTK and Java programming, a few months ago I needed to start hacking on a MFC project. I tell you, never ever again. I'm now having a cronic headace, thanks alot MS.
And what is it with those API's on Windows, do they have to typedef _everything_ for every different occasions, I'm sure I encountered 20 different typedef s for "unsigned int" just browsing through some MSDN pages. Not to mention the joy of unwinding a structure so you can get to business. Theres a structuer with a structure, member, with a member,with... And they each have members of type unsigned int, WORD, p_WORD, uint32. If somone know how to make apis and code even more unreadable I'm sure there is an open job somewhere near Redmond.
Slashdot Mirror
Strange I dont encounter this that much in the posix world, which runs everywhere, atleast not within the sae library/API. I rather suspect their mess comes from the fact that they have to keep binary compability. And that MFC mostly a wrapper a round the Win32 API, to which they change their internals with virtually every build(or so it seems). Its though a pretty bad excuse, the thing is to do it right from the beginning.
ohh. Someone a while ago told me about wxWindows. So ahead I went an tried to make my first small test app. During that hour I decided that wxWindows is crap. While abit better than MFC, theres much of the same. And i truly dislikes MFC.
I've been doing lots of Qt, GTK and Java programming, a few months ago I needed to start hacking on a MFC project. I tell you, never ever again. I'm now having a cronic headace, thanks alot MS. And what is it with those API's on Windows, do they have to typedef _everything_ for every different occasions, I'm sure I encountered 20 different typedef s for "unsigned int" just browsing through some MSDN pages. Not to mention the joy of unwinding a structure so you can get to business. Theres a structuer with a structure, member, with a member,with... And they each have members of type unsigned int, WORD, p_WORD, uint32. If somone know how to make apis and code even more unreadable I'm sure there is an open job somewhere near Redmond.