Hi,
ext Frantisek Dufka wrote:
>> And if the game doesn't disable the double pixeling properly (e.g. if it
>> crashes or freezes), user needs to reboot the device. Not very nice
>> either...
>>
>
> So what happened to idea mentioned here year ago to modify Xsp (or
> whatever) API so that pixel doubling is flag of each display update
> separately? I.e. every update would be not pixel doubled unless told so
> by flag with each update. This is how it works on kernel framebuffer
> level anyway.
>
> It is bad to turn in on and off because any other display update
> (infoprint) can mess it up. If we had blitting API in Xsp with pixel
> doubling flag settable per update this problem would go away.
>
> Well in fact we have this api - framebuffer ioctl but it is not very
> nice solution.
>
> Daniel Stone wrote:
>>
>> I don't like it as it's far too ITOS-specific (I won't be satisfied
>> until XSP no longer exists). It'll probably be replaced with RandR some
>> time in the future, even if the fixed resolution choices are only
>> 800x480 and 400x240.
Does RandR restore the original resolution automatically when the client
requesting a specific screen size exits? If not, it's not really a
solution as then screen would still be "messed up".
Also, it would be good to support the standard resolutions like 320x200
(with black borders) so that more programs would work unmodified. Many
games/emulators want a specific resolution.
> Pixel doubled resolutions would be nice and would be improvement over
> current situation indeed. What we will miss with this solution is having
> some parts of screen pixel doubled and some not
Games can already do this on 770 by setting pixel doubling on after
blitting the more detailed graphics. But as you said RandR doesn't
support that. Besides, the infoprints would still look funny. Not
as funny as with pixel doubling, but they would be too large and
as window manager positions them right aligned, they would be clipped
from the left instead of right like with Xsp. :-)
What is really needed is a flag that is window specific.
> like nice control area with nice static graphics and main pixel
> doubled game area.
I don't think it would be a great loss if the whole window would be
pixel doubled. The screen is 226 DPI. Pixel doubled it would still
113 DPI, i.e. more accurate than most (CRT) monitors. A bonus would
be that game would use less memory for its graphics (as they are
smaller) and you don't need to modify the game to support two screen
resolutions.
- Eero
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
