ddudics wrote:well... know that i think about it... i guess you're right. computers are faster now so they can run applications created in MFC just as fast as they could run applications that were created in win32 api.
ddudics wrote:FYI. wxWindows is now wxWidgets
Marc G wrote:Mmm, why do you think that applications written in MFC are slower than ones written in plain Win32 API?
I do not agree with this. Perhaps if you measure the GUI response etc with precision timing functions, then you might be able to measure some small speed penatly (I am not even sure of this though!), but it would only be measurable with precision timings and not noticeable by a human user.
I mean, if you write in plain Win32 API style, you have to create your own message pump, a Windows program cannot work without it, and you have to create your own windowproc processing messages etc. MFC also does this, but it does this for you. Also, MFC is heavily used/test/tweaked over the years.
So i really don't think there is a big speed penalty.
If you know a nice way to measure performance difference between MFC and plain Win32 API, then try to write a little benchmark and lets see what the results are
Marc G wrote:Ah, they renamed it ... but the domain is still wxwindows.org
ddudics wrote:Well... i just figure that it would be slower. I mean, if you think about it, the MFC are just wrapper funtions; so wouldn't they just be calling the same win32 api funtions? So, then theoretically, wouldn't it take less processing power to just call those functions directly instead of calling functions that call functions?
Users browsing this forum: Yahoo [Bot] and 1 guest