[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Saturday 22 July 2006 21:20, Jon Rafkind wrote:
> The program doesnt seem to respond to keyboard input at all in 320x200
> mode. I changed the resolution to 640x480 for exflame and then keyboard
> input worked.
Almost sounds like it's grabbing a Linux console mode for 320x200, but using
the X system driver (in which case you won't get input).
Perhaps it would be best to not allow Allegro to compile with both X and Linux
console support at the same time. It causes nothing but problems when they're
mixed like this..
> >> 3. ex3buf wants to use triple buffering now but my video card cant
> >> support this for whatever reason. ex3buf didnt need triple buffer
> >> before, why does it now?
> >
> > This is normal now. I think the video memory "emulation" was removed
> > from the X port. Evert?
>
> I dont think Ive ever used a computer that supported triple buffering.
> Wont plain double buffering work just as well in most cases?
In 4.2, Allegro emulates a video surface with a memory bitmap. When you draw
to the screen, it draws to the bitmap and screen at the same time (this is
needed because X can overwrite your screen area at any time and may ask the
app to redraw itself). You can create a virtual screen size and it'll create
a larger memory bitmap, and just offset all drawing operations to the screen
depending on the scrolling factor. This allows you to emulate page flipping,
etc. And AFAIK, if you try to use triple buffering when it's not available,
it'll act just like page flipping, except using three buffers instead of two.
If 4.3 removed this (which it should, IMO), then not even emulated page
flipping will work anymore. All you can do is double buffer. Since the new
graphics API is supposed to abstract away the screen update method, you
shouldn't need to worry about it anyway.