Linked by Guillaume Maillard on Thu 10th Oct 2002 05:44 UTC
Being a BeOS user (a purely desktop system) and because I code under Linux, I see XFree86 (v4.1 on my machine) as a user and as a developper. And this is where the problem lies. My Gnome or KDE desktops are slow in comparison with other operating systems, but XFree86, the 'engine' behind these desktops, proves me that it's not. Let's look at what I have in front of me: a dual Pentium III at 933Mhz with 512MB of memory, a Radeon 32 AIW, a modified Mandrake 8.0 powered by kernel 2.4.18.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
One I experieced some similar things with Win2k as well as Win98[some years ago]! There's seems to be a bug or limitation on WinDOZE GFX Resources (Per App).
So if I wrote years ago on SHS-101 ( http://www.s-brandenburg.de/shs-101 ) for Windoze I got a lot of these extraordinary Windoze Behaviour!
Every Button you see in this app was at that point a bmp image resource! Even the knobs (consists of 60 Frames or so) were handled that way! The total number of pictures was about around 300! Sometimes there occured this
strange behaviour.
After days of checking my code without results,
I tried to put all frames of the knob into one larger picture! And it worked ...
You can still experience the same thing sometimes with the ppModeler app.
-A
PS:Maybe that I am wrong, maybe that there's another bug in the WIN32 API.