Re: [ruby-fltk-devel] Top-level and child windows

[Kevin S. <kev...@ya...>]

--- Takaaki Tateishi <tt...@ja...> wrote:
> How about adding another singleton method something like
> `Window.toplevel', `Window.new2' or `Window.create' for
> creating the "top-level" window?

I thought of that, but EVERY app will have a toplevel
window, but only a few apps will have child windows. So I
think the default (if there is one) should be toplevel.

The other way would be to disable new and require users to
choose Window.toplevel or Window.child. I don't like the
name 'child' here, because it is not clear that you are
creating a child--it sounds like you might be getting the
child of a window. Maybe Window.popup would work.

So, I see three options, and any are ok with me:

1. Window.new normally creates a toplevel, but if you pass
an extra Fltk::CHILD_WINDOW at the beginning, it creates a
child.

2. Window.new creates a toplevel, and Window.popup creates
a child.

3. Window.new is disabled, Window.toplevel creates a
toplevel, and Window.popup creates a child.

I think I like #2 the best, because people looking at the
C++ FLTK docs who just want a simple window will expect it
to work.

Kevin

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com