Lifecycle events

[czyzby]

Currently it's impossible to register lifecycle events or post Runnable instances. The application implementation should invoke all posted runnables during rendering.

[soywiz]

I think this part could be totally generic if libGDX provided an Application adapter for this.

[czyzby]

You're right, but it isn't the first time LibGDX API isn't as clean as it could be, unfortunately. ;)

[soywiz]

I will create an adaptor class, but I will keep it here. Maybe we can PR libGDX suggesting to include it in its main codebase.

[soywiz]

Fixed? When are Runnable supposed to execute? Before rendering? After rendering? Since there were no removePostRunnable I suppose they are executed just once

[czyzby]

Yes, they are executed once and removed from the queue. I think they're usually executed before rendering.

Keep in mind that runnables can post other runnables (which can post other runnables, and so on) - it might make sense to avoid using a Queue. If I'm correct, GWT copies the runnables collection (if any runnables are present) before execution and clears it, so any extra posted runnables are not executed on the same frame. An endless loop due to runnables posting does seem like a programmer's error rather than framework's fault, but I think preserving the original LibGDX behavior is pretty important.

[soywiz]

Check wether this test represent the expected behaviour:
818bc81#diff-e759478f1c1ce48be118e008744fc3cdR46

[czyzby]

Yes, I think this is how it should work - or at least how it will work on GWT and LWJGL.

[soywiz]

Cool. I'm closing it.