Gustavo Sverzut Barbieri wrote: >> > It's easy for us (developers) but it is stupid, because Freevo >> needs to >> > recalculate everything everytime >> >> Only on startup. When Freevo starts, he recalculates the geometry >> values in the 800x600 skin to fit the current resolution. At runtime, >> there is no scaling at all. So no stupid pygame scaling. > > As you said, at every startup we need to recalc :)
This happens very fast, and only on startup. I don't think anyone will notice the difference. Maybe having background images for different resolutions may help. >> For the idle bar I was thinking about: if idlebar, then set skin >> width to with - some-value. ONLY at startup! All other values will >> be transformed to the new geometry. > > Ok, but and about the internals? I mean, every y0 pos will be > subtracted idlebar_height? You may get strange results... I won't subtract the idlebar_height, I will recalc y0 to avoid drawing outside the screen. We're doing the same right now when you use smaller resolutions than 800x600. > Anyway, I like the idea to have an easy way to test freevo. But for > releaseses, I prefer the one file per resolution... I don't see the difference. The only differences are the geometry values and they are identical with the 800x600 values scaled down on startup. Dischi -- Q: Why do programmers always get Christmas and Halloween mixed up? A: Because DEC 25 = OCT 31 ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
