Followup: I was able to trap the Enter key on this device by setting KeyPreview = TRUE and then monitoring Output_KeyPress(key) for key=13.
--- In [email protected], "George Henne" <gh@...> wrote: > > I think will need information from people who have worked with this device. > We have not had one here. You'll need to do some experimentation. > > >I waved my magic wand and got the scanner issue resolved but still > >having trouble trapping the Enter key. > > > >A simple "TextBox1_KeyPress(key)" will capture many keys but does not > >trigger at all on the hardware Enter key. Should I be watching for some > >other event instead? > > > > > > > >--- In [email protected], "carmine_castiglia" > ><carmine_castiglia@> wrote: > >> > >> Hi, George. > >> > >> Having a couple of issues here and hoping you can help with resolution. > >> > >> Device is Symbol MC-9060 running Pocket PC v4.2.0. The app is > >expected to capture three pieces of scanned data plus one keyed entry > >then write the record to a file and reset for the next record. > >> > >> 1) my app relies on trapping the Enter key as a means to advance the > >input to the next field using SetFocus. This works when testing with > >the WinMobile 6.1.4 emulator but not on the device. > >> > >> 2) I cannot trigger the scanner on the device. I know it is > >functional as it works with the built-in "Rapid Deployment Client." I > >have tried the Symbol sample app, following the directions in Tech Note > >27 without success. Of course, scanning within my app doesn't work either. > >> > >> Any thoughts? > >> > > > > > > > > > >------------------------------------ > > > >Yahoo! Groups Links > > > > > > > -- You received this message because you are subscribed to the Google Groups "nsb-ce" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nsb-ce?hl=en.
