Re: 4X3 Matrix Keypad design

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Peter (Peter_at_discussions.microsoft.com)
Date: 06/16/04 

Date: Wed, 16 Jun 2004 07:34:46 -0700

Thanks for your timely inputs.

"Dean Ramsier" wrote:

> If your device will support a USB keyboard, then you'll need to have a
> regular keyboard driver, because USB now makes use of some functions in the
> keyboard driver. Otherwise, you don't need one at all. Your keys are just
> another hardware device, and you can choose to interact with them in
> whatever way you desire.
>
> One option you might consider is to include the NOP keyboard driver, and
> then write a separate driver for your keyboard. It comes with a little bit
> of code space overhead, but it will provide the system (gwes) with a fully
> functional keypad interface. You'd also be able to use functions like
> keybd_event() to send keys from your simple driver to your application
> without writing a custom interface. I'm not sure if that would work without
> providing a stubbed out keyboard driver for gwes. It would also provide the
> support that a USB keyboard would need, if you need to support that.
>
> You should be able to leave all keyboard drivers out, and continue with your
> existing plan of a fully custom, simple interface if you like. I've never
> tried it, but I don't think gwes should have a problem running without one.
> --
> Dean Ramsier - eMVP
>
>
> "Peter" <Peter@discussions.microsoft.com> wrote in message
> news:122A0D7C-672A-43AB-9B73-8D67011E134D@microsoft.com...
> > Hi all:
> > I started a keypad design. My keypad is a very simple one. Has only 11
> keys. 4X4 matrix keypad. Col 4 is not used.
> >
> > The WinCE OS not visible to the user. During startup my application will
> be launched and these keys will be used to traverse the application screens.
> >
> > Hence, I don't need any Virtual Keys / Unicode and all here I believe. I
> thought of making a monolithic driver which just put any value (/ Virtual
> Key) in a message queue / buffer.
> > Then, this value will be read by Application and act accordingly.
> >
> > Here, my question is: If implement a keypad driver without any interaction
> / registration with OS, will it be a problem? I am looking for design
> constraints here.
> > Or do I need to go for an extensive driver similar to the one specified in
> the WinCE Help.
> >
> > Please guide me. Give me tutorials / direction where i can learn more
> about matrix keypad implmentaions for WinCE.
> >
> > Thanks in advance,
> > Peter.
> >
> >
>
>
>

Relevant Pages

  • Re: If I suddenly disappear...
    ... ye modifier keys. ... for pressed keys. ... the keyboard driver, which in Windows would be a .drv or .sys file. ... available to user apps to play with. ...
    (uk.rec.sheds)
  • Re: PB 4.2 error in keypad [Del.] key maping in RDP session
    ... thus we can't sell any developed platform with CE ... in numeric keypad in terminal session. ... >without having to rebuild the keyboard driver. ... >> keyboard with standard 104 keys. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: PB 4.2 error in keypad [Del.] key maping in RDP session
    ... The layout manager provides a mechanism to remap keys to various locales ... without having to rebuild the keyboard driver. ... of custom keyboard drivers, where the driver is included as part of the BSP ... >>key functionality and not just locale issues. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: 4X3 Matrix Keypad design
    ... "Dean Ramsier" wrote: ... > regular keyboard driver, because USB now makes use of some functions in the ... Your keys are just ... > support that a USB keyboard would need, if you need to support that. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Keyboard is not detected in WINCE 6.0
    ... send keys to the keyboard driver loaded by GWES. ... keyboard driver is needed to support USB keyboards. ... USB HID Keyboard and Mouse only ...
    (microsoft.public.windowsce.platbuilder)