[Suggestion] WindowFrame destroy() should be close()?

If you found a bug in our library or on our website, please report it in this section. In this forum you can also make concrete suggestions or feature requests.

Moderators: CEGUI MVP, CEGUI Team

Turbine
Just popping in
Just popping in
Posts: 1
Joined: Fri May 23, 2014 07:08

[Suggestion] WindowFrame destroy() should be close()?

Postby Turbine » Fri May 23, 2014 07:14

Generally consistency results in intuitive design.

Each WindowFrame has a CloseButton, therefore to close the window (not hide), a close() call would be the logical choice rather than destroy.

What do you think? Perhaps close() could just be an alias for destroy()?

User avatar
Kulik
CEGUI Team
Posts: 1382
Joined: Mon Jul 26, 2010 18:47
Location: Czech Republic
Contact:

Re: [Suggestion] WindowFrame destroy() should be close()?

Postby Kulik » Fri May 23, 2014 09:42

You can do whatever you want when the close button is clicked. Not everyone will want to just close the window. By default nothing happens and you have to subscribe to the event.

By WindowFrame you mean CEGUI::FrameWindow?

Using destroy() for widget destruction is consistent, using close() for just FrameWindow and destroy() for everything else would be inconsistent. I don't really see the point in this change.


Return to “Bug Reports, Suggestions, Feature Requests”

Who is online

Users browsing this forum: No registered users and 2 guests