[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [paragui-users] re: eventDraw vs eventBlit
From: |
Alexander Pipelka |
Subject: |
Re: [paragui-users] re: eventDraw vs eventBlit |
Date: |
05 Jul 2002 19:25:48 +0200 |
Hmm,..
If you have plenty of memory (so much that you can waste it) and many
widgets look differently, use widgets with widget-surface. Blitting will
be faster.
If you have many different widgets and want to keep an eye on the memory
footprint, use widgets without widget-surface.
It depends on your needs. Both ways are possible.
I personally use mostly widgets without surface because my apps have to
run on embedded devices. But they also run fast.
I would prefer eventBlit() but you will know more details about your app
:))
Alex
Am Fre, 2002-07-05 um 19.03 schrieb Keith Swyer:
> ok, didn't see that in the DOC till just now..... anyway, maybe i should
> explain myself a little more. i'm working on a widget that is a piano
> keyboard. on a note on event, i highlight the key in the widget and on note
> off i unhighlight that key. but i'm confused as to what do to, use eventDraw
> with a widget surface or just eventBlit. is one faster than the other...i'm
> assuming the blit is. and why would you ever use the draw if you can just use
> a blit? i understand that the draw is sort of saving to the widget surface.
> correct? so am i right in saying that the draw is not called on a blit unless
> specified and thus would result in faster blitting rather than redrawing the
> entire surface again? phewf, hope i didn't get lost there.....i'm just
> looking for the best way to get this keyboard showing a keypress as fast as
> possible. right now i'm only using the eventDraw for everything, but i think
> i'd be better to use a combination of both correct? draw the main keyboard
> and blit the highlights? anyway, this was a widget i made a while ago and
> now am finally using .
>
> --Keith