VisualBoyAdvance-M

heh, well it was pagefault that suggested WTL, but i guess Win32 is the better option.

 

I'll look at the VBA 1.6 source code, because apparently they didn't use MFC back then

Using Win32 would be pretty masochistic. MFC isn't pretty but it saves you from writing a huge amount of boiler-plate code.

 

Cheers,

Col

Personally, at least pure Win32 code is clean.....hence why I use it for all my personal stuff.....

Exactly.

Win32 is "Clean" says Mr Mudlord... "Exactly" concludes Mr Leonhart.

 

Your exact meaning evades me. Though I think I understand the bigger picture.

 

Take it easy,

Col

He means even though its a wench to code, its less forgiving of bad coding, making the code cleaner in the long run and better optimised

Your exact meaning evades me. Though I think I understand the bigger picture.

 

Namely because MFC can be bloated (all those extra wrappers). Like .NET. Hence why I don't use it at all.

I know that both of you will be aware that optimization should be carefully targetted and the performance of the UI isn't an issue here. Not by a long shot. On this basis, fiddling around with the existing UI becomes wasted effort. Effectively, you are running on the spot to implement personal preference for minimal gain.

 

A practical, useful way of moving forward would be to decouple the core and hide it behind an interface so that it can be updated/tested/replaced with no impact on the UI.

 

I guess the question is then: what is the long term goal?

 

Cheers,

Col

Actually, the UI is a key point of poor emulation performance when using either D3D or OpenGL due to not being able to lock the surface. Thats partly why the fullscreen menu was promptly removed.

Are you saying that MFC is preventing you from locking a D3D surface?