Albrecht Schlosser schrieb: > Michael Schmid wrote: > >> I have the following problem with FLTK 1.1.9 : >> (It's a bit a long explanation, but maybe this helps to better >> understand what the problem is :-) ) > > Following your description below, I don't think that this has anything > to do with FLTK, but see comments below. Maybe they can help you to get > an idea. > >> I have my "main window" which covers the whole screen. Then I have >> some input fields where I can type in some values. As soon as I click >> on an input field, a keyboard appears on the screen (because I have a >> touchscreen), when i press the "enter" key the keyboard dissapears. > > Which magic makes this keyboard appear? And while you are typing, where > does this keyboard process (or the window manager/OS) know from, where > to deliver the keyboard events?
I create the new process, as soon as I get a callback form the input field (if I push on the input) > >> This keyboard is a seperate process, so its no FLTK-Keyboard (I know >> it would be possible to make my own and I know ercos example which is >> great, but I have reasons to use this other keyboard) >> OK, as soon as I complete the last input field, there is a check if >> the values in the fields are valid. If not, a popup appears which >> informs about the invalid value. AND THIS POPUP IS A SEPERATE WINDOW >> -> IMPORTANT :-) > > What kind of window is this? Is it modal? Is it something like > fl_message(), fl_alert() or similar? It is a modification if the programm nxkbd (delivered with nano-x window) > >> Know, if I reopen the keyboard-process (by clicking on an input field >> again), > > what happened to the other window ? Did you close it? yes, i killed the process > >> the input fields don't get the keyboard events (or maybe they do, but >> the characters don't appear in the field) any longer... It seems that >> the main window has lost its keyboard-focus... :-( > > If this is so, then FLTK can't do anything against this. After all you > wrote "by clicking on an input field again". What is different? > > Would it change anything, if you click somewhere else in the main window > first to make it "active" (get the input focus) before clicking on an > input field? > >> Has anybody an idea what the problem could be? > > I can only think that the same "magic" that works in the first case > doesn't work here. But since this has to do with other software (the > keyboard process) and/or the window manager and/or the OS, it is more > than difficult to guess ... > >> I use the Nano-X Window System (Version 0.91) and Linux 2.6.24. >> >> I have no clue where the problem is! .... >> >> Thanks for every hint! > > Did you try this with other applications? How do they behave? Other than > debugging X events I don't have any more hints. Are there any docs how > this keyboard process integrates into the OS? Did you think of asking > the touchscreen producer for help? > > Okay, one more idea: After closing the popup window, can you call > something like main_window->show() to get it to the top of the window > stack (even if it looks as if it is anyway)? I'll try... Thanks! > > Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
