Is a good idea mantaining input and window managemente at Xlib level? about monocle-engine HOT 7 CLOSED

I'd rather not use a library if we can avoid it, so we can have more control and have more flexibility when it comes to porting to new platforms.

If enough people end up using the engine, I think we'll be able to isolate and test platform issues fairly quickly as they come up. So far it seems to be working pretty well?

from monocle-engine.

In linux there are some problems in the TestOgmo test. Jump height seems to be completely random (i don't know if the bug is in game code but i think that there's some platform specific problem). About my proposition i was just thinking out loud... i totally get your point
I'll investigate the problem sticking to the actual implementation.

from monocle-engine.

My guess would be the timing code on Linux, it seems to behave differently than on other platforms for some reason. :)

from monocle-engine.

i.e. Monocle::deltaTime

from monocle-engine.

mmmm I'm not sure... i've just changed and committed the time code for linux platform to reflect the cocoa one and the random jump issue is still here.

from monocle-engine.

The problem was in the demo phisics logic... applying deltaTime on velocity pulse makes jump and movements in general frame rate dependant. I'll fix the demo and commit the correct code.

from monocle-engine.

Cool, thanks for the fix. :)

from monocle-engine.