Messages

1

Window / Re: Wait for events in a real blocking way

« on: February 08, 2015, 12:28:37 am »

Is there anything you have already tried/benchmarked, or are you just overthinking it?

I remember to have tried Sleep(0) on Windows and sched_yield() on Linux and they didn't work well. The "final" solution was this: https://github.com/aseprite/aseprite/blob/master/src/ui/message_loop.cpp#L35 (pretty close to what SFML does)

Anyway the CPU usage depends on the amount of work needed for the polling. I think that my case (checking some Allegro 4 structures, like an key[] array) is much worse than SFML (maybe a simple PeekMessage() and events.empty() check).

Usually, I would also answer that SFML is not the right library for such an application, and would advise to use Qt or similar. But I guess it would be hard to get that pixelated look that your application has.

Yeah. Anyway I think I'll have a hybrid solution in the future (parts of code with SFML/or other 2D library like Skia/Cinder + other native parts, e.g. Cocoa, Win32 controls, etc. Both interfaces: pixelated and native).
Thanks for your time!

2

Window / Re: Wait for events in a real blocking way

« on: February 07, 2015, 09:07:37 pm »

Why is this so important for you?

I'm changing the back-end of my application (http://www.aseprite.org/) to support multiple windows. At this moment I'm using a customized version of Allegro 4 library, and busy-wait is something I would like to eradicate (I've a similar fix to avoid 100% CPU usage). I was considering SFML as a replacement, but I'd like to avoid using more CPU that needed (e.g. to improve battery life). (For video games it doesn't make sense to avoid polling, as rendering is going to happen anyway, but for applications without constant animations, it does make sense.)

3

Window / Wait for events in a real blocking way

« on: February 07, 2015, 07:35:08 pm »

Hi! Is there any method to wait for events in the real blocking way as the OS expect? (e.g. using GetMessage() on Win32 API).

I've found this:
https://github.com/SFML/SFML/blob/f24ca9a84012531cf886f72354c1f88341dd7ac7/src/SFML/Window/WindowImpl.cpp#L125

It is a busy wait with a sleep to avoid high CPU usage. From the comment in that line it's just because the joystick input events needs a polling mechanism, but my question is, could we just use a real blocking method if we don't need joystick input? (e.g. I'm developing an application and I don't need joystick input)

Thanks!