> > If this code is called more frequently than that, it should probably
> > use the main select() loop (and create a main select() loop for the
> > framebuffer GUI, there are good reasons why every other GUI does this).
>
> I'll think about for the framebuffer GUI post release, as I'll be
> doing other work to it. The problem with the main select loop is it's
> event based, and jumps to a callback. That way it gets ugly to access
> the movie_root data to make method calling, etc... actually work.
>
> By being deep inside the movie_root advance, if there is a remote
> function, it's then easy to do something with it. Some of the other AS
> classes work the same way for the same reason.
Yeah, I'd have the main loop stuff just set a variable (either telling
us that there's data on that file descriptor, or actually reading in the
data and putting it in the variable). Then in the movie_root advance,
you examine the variable and take action if set.
John
_______________________________________________
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev
