Michael Schmid wrote:

> No, it really want a modal window (so the widgets of the parent window 
> shouldn't be active as long as the modal window is there)
> 
> I try to explain my configuration again:
> 
> parent window -> child window (modal)
> child window -> contains OK Button
> OK Button -> callback which closes child window (hide())
> 
> So if I press the OK Button, the callback isn't performed... As I said 
> before, it seems to be a kind of a deadlock... (Child window doesn't get 
> the event because the modal-option blocks event propagation to the 
> childs of the parent window...

This is not how it should work. If the child window is modal(), then the 
*child* 
window should get all events (and drop those that are not for the child).

This is, how all the fltk dialog windows work.

> Or is there another reason why this doesn't work?)

There must be another reason, or your description (or program) is wrong and 
doesn't do what you described. Maybe this is really a bug in Nano-X, as Ian 
suspected.

> Is there another way to do this? Or is this approach wrong?

The approach you described looks perfectly okay. Maybe you should really try 
another X server, if this is possible, otherwise you'll never know. Or try a 
simplified test case on both Nano-X and a normal desktop system with another X 
server, and see what the differences are (as Ian suggested already).

Albrecht
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to