Re: [AD] RFC - Linux WM Fullscreen Patch

[ Thread Index | Date Index | More Archives ]

The information I was given by someone here before was that the "WM Fullscreen" ie ALLEGRO_FULLSCREEN_VIRTUAL mode would be scaled up but it wold be all done without the user having to worry about it and behave exactly like ALLEGRO_FULLSCREEN otherwise.

In actuality, as I learned today, it's almost identical to ALLEGRO_FULLSCREEN. The only difference is, some WM flags are set when supported. The reason we didn't combine ALLEGRO_FULLSCREEN and ALLEGRO_FULLSCREEN_VIRTUAL before was that someone said the scaling would be a problem on certain hardware ie they needed it to be exactly like a hardware fullscreen mode. However, I found out today that it is exactly the same as a real hardware fullscreen mode.

So IMO the best thing to do is to remove the ALLEGRO_FULLSCREEN_VIRTUAL flag and use the code paths I just added all the time (they check for support first.) I don't see any drawback of doing it that way, in fact SDL does the same thing, so if anyone has legitimate objections bring them up now.

----- Original Message ----- From: "SiegeLordEx" <slabode@xxxxxxxxxx>
To: <alleg-developers@xxxxxxxxxx>
Sent: Thursday, August 07, 2014 1:16 PM
Subject: Re: [AD] RFC - Linux WM Fullscreen Patch

On 08/07/2014 02:58 PM, Trent Gamblin wrote:
Looked at SDL closer - it behaves differently than I was told. It
doesn't scale at all, it uses the window manager to go fullscreen and
then xrandr/xvidmode to change the mode. Better for us, I did the same
and the patch is a ton simpler now.

I'd like to propose changing ALLEGRO_FULLSCREEN_WINDOW so that it
implies ALLEGRO_FULLSCREEN as well. That'll require a few changed checks
here and there but not as bad as making ALLEGRO_FULLSCREEN separate from
have been that way from the start, as a modifier.

What does this implication mean exactly? Will you be able to do
mode-setting via ALLEGRO_FULLSCREEN_WINDOW? I note the patch doesn't
seem to do that...

This wasn't really clear from the fullscreen thread earlier either...
what are the use cases for the 3 separate FULLSCREEN options? In the
current system, you use ALLEGRO_FULLSCREEN for performance (i.e. want
direct access and/or don't want to have a buffer bitmap + scaling) with
the caveat that it doesn't work well on modern monitors and
ALLEGRO_FULLSCREEN_WINDOW otherwise (i.e. most of the time). Does the
current plan change that reasoning? If the scaling idea is (at least
temporarily) abandoned, what is the use case for ALLEGRO_FULLSCREEN_VIRTUAL?

Is there no way for ALLEGRO_FULLSCREEN_WINDOW and


Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.

Mail converted by MHonArc 2.6.19+