SFML community forums
Help => Window => Topic started by: Kobie on December 21, 2010, 12:57:51 am
-
Edit: Deleted.
-
the window could simply be hidden by default until Window::Display() is called
Hum that's an idea, I'll think about it for SFML 2.0 (SFML 1.7 is not going to exist).
-
In fact the idea to have the window hidden until the first call to Display() looks really cool. It makes sense because until Display() is called, the window will show garbage -- so it's not even a hack.
I'd like to know what other users think about it. Would there be any drawback doing this automatically?
-
I prefer to use clear() to init window, because I have test prog whithout Display() :D.
If the window is hidden, the events are recovered???
-
I prefer to use clear() to init window, because I have test prog whithout Display()
Hum... that looks weird. Can you tell me more about what you do? How can you see something useful without calling Display()?
If the window is hidden, the events are recovered???
It depends. Which events?
-
I can see why it would be useful but its also not hard to quickly create the window and throw up a logo or something while everything else gets loaded. Of course having the window hidden until the first call of Display() doesn't stop anyone from doing that so I don't see any reason not to implement it if its not too difficult on Laurent.
-
I'm so-so with this technic – my main concern is about the current Show(bool) function. Could we still be able to use such functionality ? – but I like the idea!
From all GUI lib I've worked with all have the same pattern : call explicitly a 'show' method to display the window. Why not having to call this Show(bool) function to explicitly put the window on screen and by default having the window hidden ?
-
my main concern is about the current Show(bool) function. Could we still be able to use such functionality ?
Why not?
From all GUI lib I've worked with all have the same pattern : call explicitly a 'show' method to display the window. Why not having to call this Show(bool) function to explicitly put the window on screen and by default having the window hidden ?
I never do things just because all other libraries do it, I only do things which are relevant and well designed ;)
If we can do without explicitely using Show(true), that's a lot better. And it will avoid tons of forum topics like "I don't see my window what happens???" ;)
-
So I don't have any concern about it! =)
I never do things just because all other libraries do it, I only do things which are relevant and well designed ;)
Yeah, I know that : you're always way ahead of us (or at least me hahaha)!