[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
nxkbd bug or feature
From: "E.Allen Soard" ####@####.#### Date: 26 Sep 2001 17:53:38 -0000 Message-Id: <3BB21734.4000707@espsw.net> I noticed that with the nxkbd demo that the virtual keyboard refuses to come to the top when it ganes focus (both under X and on my ipaq using the frame buffer) is this a bug or a feature? -E. Allen Soard | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] nxkbd bug or feature
From: "Greg Haerr" ####@####.#### Date: 26 Sep 2001 20:30:35 -0000 Message-Id: <013701c146cb$c962df10$6817dbd0@censoft.com> : I noticed that with the nxkbd demo that the virtual keyboard refuses to : come to the top when it ganes focus (both under X and on my ipaq using : the frame buffer) is this a bug or a feature? This is a result of the nxkbd window having the NOFOCUS bit set, and the nanowm window manager using focus events to determine when to bring the application to the top. Perhaps this could be solved in a different fashion, by modifying nxkbd or nanowm. Normally, the keyboard is placed in a different, known screen area where this isn't a problem. A quick fix would be for nxkbd to call GrRaiseWindow whenever it gets an event... Regards, Greg : : -E. Allen Soard : : : : --------------------------------------------------------------------- : To unsubscribe, e-mail: ####@####.#### : For additional commands, e-mail: ####@####.#### : | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |