SFML community forums
Help => General => Topic started by: luqsthunder on April 04, 2016, 02:30:51 am
-
Hi guys, I am trying to use a GUI library for my game, like cegui, but for some reason it runs too slow, I tested with some examples, one which uses cegui https://github.com/ghtyrant/SFML_CEGUI, it is the same from sfml github wiki but already updated to cegui 0.8 and sfml 2.1. Also I tried another library called libRocket.
Bellow is the example: https://github.com/libRocket/libRocket/tree/master/Samples/basic/sfml2/src
It is fast to compile and it also uses cmake.
Here is what occurs:
(http://postimg.org/image/ptlw8iw47/)
(http://postimg.org/image/kw8bneu53/)
Maybe I am being too fussy (as this message is shown but nothing went wrong) but in a professional game that message should not appear.
This is the first example I've seen: https://skyr.at/sfml-and-cegui-083.html.
I need help to figure out how to get my code fast or why this message is showing up and also to figure out a workaround if possible.
-
If app doesn't respond that doesn't respond that doesn't mean that it slowed down, It may be crashed.
-
Are you processing the SFML events? You have to otherwise the OS marks your application as unresponsive.
-
I looked at example and... I don't like this part of code:
static sf::Event
-
I think that rocketLib "debugger" may slowdown your program.
-
Please stop throwing random thoughts around. Either be certain (and really be correct) or keep it to yourself. Wrong/misleading information is more annoying and time wasting than no answer at all...
-
Why don't you stop your program in debugger and see where it hangs?
Or you can use profiler. Or logging.
-
If app doesn't respond that doesn't respond that doesn't mean that it slowed down, It may be crashed.
it respond, only show this message.
Why don't you stop your program in debugger and see where it hangs?
Or you can use profiler. Or logging.
Its a good thing use a debug, but I could not figure out while using a debugger, because the only this message appears and nothing changes, so like eXpl0it3r said is a thing of treating window events
Are you processing the SFML events? You have to otherwise the OS marks your application as unresponsive.
So if I do something that takes a long time and forget to treating events this message will appear?
Like loading many things to the game and/or making random procedural generation content.
I solved creating the window just after loading everything, and functions / methods that require a valid OpenGL context, I put a sf :: Context, then that means solved, thanks :)
now i will try to make a loading screen and see how deal without using threads, or just ignoring the window events.
-
So if I do something that takes a long time and forget to treating events this message will appear?
Like loading many things to the game and/or making random procedural generation content.
Yes.