I want the gui to be just a wrapper for the training application, such that any operation could be done in console mode also. That's why I don't want to use a button on the screen.
But I got another alternative and I'll go with that. event1 is the touchscreen, and I'll use that to slice the signal. Remember that only I will need to train the classifiers, and models won't need to be trained with pushing the touchscreen. Other people will train only the models for a better recognition accuracy. Paul On Thu, Jul 10, 2008 at 3:41 PM, The Rasterman Carsten Haitzler < [EMAIL PROTECTED]> wrote: > On Thu, 10 Jul 2008 12:39:36 +0300 "Paul-Valentin Borza" > <[EMAIL PROTECTED]> babbled: > > > Can anyone tell me how can I intercept the AUX button (i.e. detect when > the > > AUX is pressed and when it's not)? > > I need a button in order to train the classifiers on the Neo; for the Wii > > I've used the A button. > > The models don't need pushing any buttons when they're being trained, > > because motion is detected with the classifiers. > > AUX is a key in X. the problem is it probably has already been captured by > the window manager for things like managing apps or the overall "system". > you > can lock out the wm's key grabs by grabbing the whole keyboard - this does > mean > though that any system management bound to those keys will cease to work. > > my suggestion is to ignore the buttons - there are only 2 and they are > already allocated for tasks to manage apps (eg flip applications, close > them, > bring up an app menu, lock the screen etc. all depending which image you > use). > > use a button widget on the touchscreen. leave the hardware ones alone - too > few > of them :( > > -- > Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> > -- http://www.borza.ro
