RE: R: R: R: [AD] Allegro 5 new config routines, alpha 1 |
[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]
> Why? This sounds like over-optimization to me. Hopefully
> nobody is going
> to access config variables very often? (At least that seems to be the
Well, some would be accessed quite often if the following were
to become true:
> currently I've made that you can assign a read/write hook function to
> each node, so for example you can assign an hook that updates internal
> vars when accessing the directory "/keyboard/state/" (example directly
> from Shawn's thoughts online, go reread the thing), so that you know the
> current state of "/keyboard/state/AL_KEY_SPACE" for example, as to
> access AL_KEY_SPACE the system first scans the /state/ dir, finds it has
> an hook and calls it.
--
Vincent Penquerc'h
Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |