[ 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] float positions
- From: Elias Pschernig <elias@xxxxxxxxxx>
- Date: Mon, 22 Jan 2007 17:37:42 +0100
On Mon, 2007-01-22 at 16:25 +0000, Victor wrote:
> OTOH non-integer pixels positions could slow down many allegro programs
> which put/get integer pixels and blit in integer bitmap positions.
Assuming that the OpenGL drivers will be the fastest available drivers,
and those already use floating point natively, I doubt it. Also, on
desktop computers, there won't be a performance difference in using
floats or int.
Even if Allegro is to be ported to some kind of handheld device which
doesn't support floating point in HW, it shouldn't run slower. If you
try to compile a program which already uses float, they simply are cut
to ints (won't affect performace, as one conversion / gfx API call can
be neglected compared to the vtables, clipping and color stuff going
on..).
> May
> create some caveats on lots situations too.
Which ones?
> It would be better to create new functions to put/get non-integer
> pixels and use non-integer blit, without deprecating or changing the
> existing ones. Its important to note that they don't need to use
> OpenGL, it's feasible and not very complex to implement they by hand
> _IF_ needed for whatever reason.
There are no existing ones as it is yet to be written..
--
Elias Pschernig