From: David C. <D. C. <si...@te...> - 2000-04-20 21:35:58
|
Thank you everyone for discussing these issues; I'm learning a lot. I see some people are referring to my pySDL documentation as they try to determine what's going on, so I'm going to say this as clearly as I can: ---> I don't really know what I'm doing. <--- This has two obvious results: 1) The documentation is incomplete. If you come up with any insight into the workings of SDL and pySDL, please let me know. If you feel that parts of the documentation are unclear or poorly worded, please tell me. You don't even have to supply replacement wording (as Martijn so kindly did), just tell me "Your explanation of x sucks." and I'll get on it. This documentation needs to be useful to the pySDL community - I'll change whatever needs changing until it is. 2) The documentation is incorrect. Don't rely on my understanding of the API for very much at this point. Read the SDL documentation too - in some cases (such as color shifts), I've just cut and pasted from there or from the __doc__ strings. Don't take what's written in the pySDL documentation as gospel until you've tested it in the real world. >> You can specify HWSURFACE, when you create the surface, and if it can't be >> allocated in hardware memory, it'll be allocated in system memory. > That must be what's happening then; I just checked and I do use HWSURFACE. > So I wonder how David found out it wasn't possible; I suppose he did > a query on the surface after creation? Nothing that dramatic, really - I just noticed that video_info(INFO_HW_A) returned 0 :) That, plus the fact that blits didn't seem to be any faster with video_set_mode(HWSURFACE vs. SWSURFACE). Eagerly awaiting 0.0.4 :) Preliminary pySDL documentation: http://www3.telus.net/futility/futility/docs/pysdl/index.html -- ------------------------------------------------------------------------- "The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts." -Bertrand Russell |