[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Event handling problems
From: "Marcel Karras" ####@####.#### Date: 30 Aug 2005 15:39:41 +0100 Message-Id: <2730.217.246.159.17.1125412775.squirrel@freebits.de> Hello, I just joined that list in order to get some help on a problem I'm still working on: I created a small nano-X application which will be used on an embedded system soon. Therefore I wrote a kind of prelimitary desktop with two icons. The desktop app itself will invoke the startup of other apps. In order to get full access to the nano-X architecture I use the nano-X API for the desktop app. All other things will be done with flnx. (fltk port to nano-X) At the moment I have a problem with the event mechs of nano-X. I created a big background window with an image (the desktop background) and 2 small windows (the app icons). Furthermore I registered the events to be used and catched them as usual. But whatever I do I'm not able to have the two icon windows recogizing the button up events. I tried several scenarios: playing around with the properties of the windows, changing the sequence of widget definitions and event registrations and so on. Can someone help me on this? I attached the main.c file in order to provide further information. Greetings - Marcel Karras [Content type application/octet-stream not shown. Download] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Event handling problems
From: "Greg Haerr" ####@####.#### Date: 7 Sep 2005 02:40:03 +0100 Message-Id: <158501c5b34c$c8e822b0$6401a8c0@winXP> : In order to get full access to the nano-X architecture I use the nano-X : API for the desktop app. All other things will be done with flnx. (fltk : port to nano-X) : At the moment I have a problem with the event mechs of nano-X. I created a : big background window with an image (the desktop background) and 2 small : windows (the app icons). Furthermore I registered the events to be used : and catched them as usual. But whatever I do I'm not able to have the two : icon windows recogizing the button up events. A couple ideas: try selecting for both mouse UP and DOWN events, there are some issues when both aren't selected. Also, I recommend using NXLIB w/FLTK rather than FLNX. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Event handling problems
From: "Marcel Karras" ####@####.#### Date: 7 Sep 2005 08:18:42 +0100 Message-Id: <4063.217.246.154.35.1126077511.squirrel@freebits.de> Hello Greg, Greg Haerr sagte: > : At the moment I have a problem with the event mechs of nano-X. I created a > : big background window with an image (the desktop background) and 2 small > : windows (the app icons). Furthermore I registered the events to be used > : and catched them as usual. But whatever I do I'm not able to have the two > : icon windows recogizing the button up events. > > A couple ideas: try selecting for both mouse UP and DOWN > events, there are some issues when both aren't selected. I solved the problem by having done the following: I just made the other windows to children of the main app window and that solved the prob. Perhaps there are conflicts if one uses more than one windows bind to GR_ROOT_WINDOW_ID. Regards - Marcel | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Event handling problems
From: "Greg Haerr" ####@####.#### Date: 7 Sep 2005 16:41:39 +0100 Message-Id: <179401c5b3c2$567b5dc0$6401a8c0@winXP> : > A couple ideas: try selecting for both mouse UP and DOWN : > events, there are some issues when both aren't selected. : : I solved the problem by having done the following: I just made the other : windows to children of the main app window and that solved the prob. : Perhaps there are conflicts if one uses more than one windows bind to : GR_ROOT_WINDOW_ID. Actually, it likely works because of the keypress selection auto-inheritance from a parent window. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |