On Aug 18, 11:36 am, René Dudfield <ren...@gmail.com> wrote:
> anyone read about immediate mode guis? (imagine immediate mode
> graphics VS retained mode graphics)
It's an intriguing concept, but it has one major drawback. Input
sampling/processing and FPS are coupled inseparably. I daresay with
mice and keyboards and standard flat GUI applications (that do nothing
else), that's not a big problem. However, if you take into account
tablets, mice, 3d controllers, etc., they generate *huge* amounts of
events quickly at high sample rates, and to worsen things, often these
events need to go into physics simulations that need them more
frequently then you draw.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to pyglet-users@googlegroups.com
To unsubscribe from this group, send email to
pyglet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
