Thanks for the infos,
doublemax.
I built the latest (git) wxWidgets 2.8 with MSVC 6.0 then finally I was able to test it on a real environment (hardware). It's a
Pentium I computer running at
120 MHz with memory
128 MB. Video card is a
Matrox Mystique with
2 MB video memory. OS was
Windows 95 OSR2.5. I got really promising results with sample applications. Application cold startup time is around 2-3 seconds which is acceptable. Warm start is around a second which I find good. All samples gave a usable interface without serious slowdowns.
However, one thing annoys me a bit. GDI drawing performance is a bit poor. Internet Explorer 4 can load even big HTML files really fast. I installed DirectX 8.0a (last available DirectX for Windows 95) which improved the rendering time of Internet Explorer but meant nothing to any sample application of wxWidgets. I can see the slowness of
richtext.exe scrolling with pure eyes. Same is true for any HTML sample app for displaying HTML (e.g. helpview). I loaded all example HTML files of wxWidgets samples into Internet Explorer 4 and scrolling performance was much better than in the own HTML canvases of wxWidgets samples. The slowest were the
grid and the
listctrl examples. Sample
htlbox was also jagging while being scrolled. Other (non-wx) native MFC applications were smooth.
Considering the fact that wxWidgets also uses native controls, is there some setup.h/config.h flag for wxWidgets to use more (or more legacy) acceleration capabilities of GDI?
catalin wrote:wxWidgets 3.0 still supports Win9x and VC6 and will continue to do it [VZ]. Just use the latest 3.0.x release or even its master branch.
That's good to know. Next time I'll try to do a working 3.0.X build with MSVC 6.0 and test it on hardware. As wxWidgets has been developed for many compilers throughout the years, I suppose MSVC compilation won't cause much problems on the wxWidgets part as the code is standardized to the level that's the most compatible. Or am I wrong?