Fast typing gets keyboard locked (sendkeys - numlock)


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 5 of 5

Thread: Fast typing gets keyboard locked (sendkeys - numlock)

  1. #1
    Naldo Guest

    Fast typing gets keyboard locked (sendkeys - numlock)

    Within our office I have some users who press the keyboard buttons at an
    incredible rate. Very frequently there keyboard locks under a windows 2000
    environment. I've reworked the code towards some articles in technet
    Q192273, Q179987, Q177674 but non of these have effect. The keyboard still
    gets locked. I'm using VB6 with SP4, and W2K with SP1. Does anybody know
    if post-SP1 service packs exist towards W2K or post-SP4 towards VS6. Or are
    there workarounds existing not mentionned in technet. Could the usage of a
    third party Input Component help instead of the Textbox control? Which
    component to use ? Or the usage of the Win32 API?

    Regards,
    Naldo.



  2. #2
    michiel de bruijn Guest

    Re: Fast typing gets keyboard locked (sendkeys - numlock)

    Hi Naldo,

    > Within our office I have some users who press the keyboard buttons at an
    > incredible rate. Very frequently there keyboard locks under a windows

    2000
    > environment. I've reworked the code towards some articles in technet
    > Q192273, Q179987, Q177674 but non of these have effect. The keyboard

    still
    > gets locked.


    I've never, ever experienced any keyboard 'locking' problems under Windows
    2000, and apart from the fact that I'm an incredibly fast typist myself, we
    also do 'monkey testing' against our apps, where the point is to press as
    many random keys as rapidly as possible to see if any unintended application
    behavior occurs. The first thing I'd check out is whether the problem is
    hardware-related: does the problem also occur on a different make of
    machine/keyboard, and does changing the keyboard repeat rate (both in the
    BIOS and Windows 2000) change the frequency of the 'lockups'?

    However, the KB articles you reference are all related to SendKeys, and you
    don't really mention anything about that in your problem description.
    SendKeys can often be problematic, especially when used across processes. In
    some cases, it can put Windows in a state where the system *appears* to be
    unresponsive. Service packs or different input controls won't help you here:
    ditching SendKeys altogether is the only realiable solution. If you need to
    transfer data into a different application without that app's cooperation,
    using SendMessage with the appropriate xx_SETTEXT-related message will work
    fine in most cases, although finding the right window handle etc. for the
    input controls can be a bit of a hassle...

    '//mdb




  3. #3
    michiel de bruijn Guest

    Re: Fast typing gets keyboard locked (sendkeys - numlock)

    Hi Naldo,

    > Within our office I have some users who press the keyboard buttons at an
    > incredible rate. Very frequently there keyboard locks under a windows

    2000
    > environment. I've reworked the code towards some articles in technet
    > Q192273, Q179987, Q177674 but non of these have effect. The keyboard

    still
    > gets locked.


    I've never, ever experienced any keyboard 'locking' problems under Windows
    2000, and apart from the fact that I'm an incredibly fast typist myself, we
    also do 'monkey testing' against our apps, where the point is to press as
    many random keys as rapidly as possible to see if any unintended application
    behavior occurs. The first thing I'd check out is whether the problem is
    hardware-related: does the problem also occur on a different make of
    machine/keyboard, and does changing the keyboard repeat rate (both in the
    BIOS and Windows 2000) change the frequency of the 'lockups'?

    However, the KB articles you reference are all related to SendKeys, and you
    don't really mention anything about that in your problem description.
    SendKeys can often be problematic, especially when used across processes. In
    some cases, it can put Windows in a state where the system *appears* to be
    unresponsive. Service packs or different input controls won't help you here:
    ditching SendKeys altogether is the only realiable solution. If you need to
    transfer data into a different application without that app's cooperation,
    using SendMessage with the appropriate xx_SETTEXT-related message will work
    fine in most cases, although finding the right window handle etc. for the
    input controls can be a bit of a hassle...

    '//mdb




  4. #4
    Naldo Guest

    Re: Fast typing gets keyboard locked (sendkeys - numlock)

    In my VB applications I'am using sendkeys to trap the <ENTER> key and
    translate it to <TAB>. With the 'Slow' users this results in flashing
    num-lock but no locks. With the fast users this results in loosing the
    num-lock so that suddenly the numerical keypath is gone;1 becomes <END>, 3
    <PGDN> ... This every 15 minutes or so. But also, and that several times a
    day, the fast users loose the complete keyboard. It's then no longer
    possible to press any key. Everything else works like mouse and software.
    The solution we've found so far is to pull the keyboard cable out of the
    back of the PC system and insert it after 10 seconds. Then the keyboard is
    back online.

    This happens on different recent types of Dell Optiplex PC systems.

    I'm having W2K SP2 and Visual Studio 6 SP4 installed.

    Thanks for the reply Michiel.

    Kind regards,
    Naldo.


    "michiel de bruijn" <mdb+devx@x42.net> wrote in message
    news:39fee8ee$1@news.devx.com...
    > Hi Naldo,
    >
    > > Within our office I have some users who press the keyboard buttons at an
    > > incredible rate. Very frequently there keyboard locks under a windows

    > 2000
    > > environment. I've reworked the code towards some articles in technet
    > > Q192273, Q179987, Q177674 but non of these have effect. The keyboard

    > still
    > > gets locked.

    >
    > I've never, ever experienced any keyboard 'locking' problems under Windows
    > 2000, and apart from the fact that I'm an incredibly fast typist myself,

    we
    > also do 'monkey testing' against our apps, where the point is to press as
    > many random keys as rapidly as possible to see if any unintended

    application
    > behavior occurs. The first thing I'd check out is whether the problem is
    > hardware-related: does the problem also occur on a different make of
    > machine/keyboard, and does changing the keyboard repeat rate (both in the
    > BIOS and Windows 2000) change the frequency of the 'lockups'?
    >
    > However, the KB articles you reference are all related to SendKeys, and

    you
    > don't really mention anything about that in your problem description.
    > SendKeys can often be problematic, especially when used across processes.

    In
    > some cases, it can put Windows in a state where the system *appears* to be
    > unresponsive. Service packs or different input controls won't help you

    here:
    > ditching SendKeys altogether is the only realiable solution. If you need

    to
    > transfer data into a different application without that app's cooperation,
    > using SendMessage with the appropriate xx_SETTEXT-related message will

    work
    > fine in most cases, although finding the right window handle etc. for the
    > input controls can be a bit of a hassle...
    >
    > '//mdb
    >
    >
    >




  5. #5
    Naldo Guest

    Re: Fast typing gets keyboard locked (sendkeys - numlock)

    In my VB applications I'am using sendkeys to trap the <ENTER> key and
    translate it to <TAB>. With the 'Slow' users this results in flashing
    num-lock but no locks. With the fast users this results in loosing the
    num-lock so that suddenly the numerical keypath is gone;1 becomes <END>, 3
    <PGDN> ... This every 15 minutes or so. But also, and that several times a
    day, the fast users loose the complete keyboard. It's then no longer
    possible to press any key. Everything else works like mouse and software.
    The solution we've found so far is to pull the keyboard cable out of the
    back of the PC system and insert it after 10 seconds. Then the keyboard is
    back online.

    This happens on different recent types of Dell Optiplex PC systems.

    I'm having W2K SP2 and Visual Studio 6 SP4 installed.

    Thanks for the reply Michiel.

    Kind regards,
    Naldo.


    "michiel de bruijn" <mdb+devx@x42.net> wrote in message
    news:39fee8ee$1@news.devx.com...
    > Hi Naldo,
    >
    > > Within our office I have some users who press the keyboard buttons at an
    > > incredible rate. Very frequently there keyboard locks under a windows

    > 2000
    > > environment. I've reworked the code towards some articles in technet
    > > Q192273, Q179987, Q177674 but non of these have effect. The keyboard

    > still
    > > gets locked.

    >
    > I've never, ever experienced any keyboard 'locking' problems under Windows
    > 2000, and apart from the fact that I'm an incredibly fast typist myself,

    we
    > also do 'monkey testing' against our apps, where the point is to press as
    > many random keys as rapidly as possible to see if any unintended

    application
    > behavior occurs. The first thing I'd check out is whether the problem is
    > hardware-related: does the problem also occur on a different make of
    > machine/keyboard, and does changing the keyboard repeat rate (both in the
    > BIOS and Windows 2000) change the frequency of the 'lockups'?
    >
    > However, the KB articles you reference are all related to SendKeys, and

    you
    > don't really mention anything about that in your problem description.
    > SendKeys can often be problematic, especially when used across processes.

    In
    > some cases, it can put Windows in a state where the system *appears* to be
    > unresponsive. Service packs or different input controls won't help you

    here:
    > ditching SendKeys altogether is the only realiable solution. If you need

    to
    > transfer data into a different application without that app's cooperation,
    > using SendMessage with the appropriate xx_SETTEXT-related message will

    work
    > fine in most cases, although finding the right window handle etc. for the
    > input controls can be a bit of a hassle...
    >
    > '//mdb
    >
    >
    >




Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center