| Re: [AD] Fullscreen questions |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: "Coordination of admins/developers of the game programming library Allegro" <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] Fullscreen questions
- From: "Trent Gamblin" <trent@xxxxxxxxxx>
- Date: Sat, 30 Aug 2008 13:57:03 -0600 (MDT)
On Sat, August 30, 2008 12:24 pm, Peter Hull said:
> I'm about to start the Mac fullscreen code which is the big thing I
> haven't done yet (dreading the debugging but at least I have a
> laptop
> I can use to ssh in and run gdb from there)
> What I'm planning is:
> You can create as many fullscreen displays as there are screens
> Windowed displays will go onto a screen that isn't captured for
> fullscreen use, if possible.
> You can override this with the api functions
> A display won't stop being fullscreen until it's destroyed (i.e. if
> you set_current_display to a different one)
>
> Is this how it works on Windows?
>
> Pete
That is basically how it _should_ work on Windows. Right now
windowed displays are always created on the primary display (which I
meant to fix but forgot about), and it doesn't check for a
non-fullscreen screen to create windows on first. I will make those
changes though.
Trent :{)>