1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Problem with Find dialog

Discussion in 'Support' started by Jim Cook, Mar 12, 2009.

  1. Jim Cook

    Joined:
    May 20, 2008
    Messages:
    604
    Likes Received:
    0
    TCC 10.00.57 Windows XP [Version 5.1.2600]
    TCC Build 57 Windows XP Build 2600 Service Pack 3

    If I click Start \ Run and launch TCC twice, then go to one of them
    and right click and select the Find dialog, then (most) keystrokes in
    the other unrelated TCC window are disabled and beep.


    --
    Jim Cook
    2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
    Next year they're Sunday.
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,860
    Likes Received:
    83
    Jim Cook wrote:

    Not reproducible here, nor can I imagine any way that this could happen
    unless (1) you're running a keyboard driver that's intercepting the
    keystrokes, or (2) you've found a catastrophic Windows bug that allows
    one process to interfere with input to another process in an unrelated
    window. (Which wouldn't be all that surprising in the console manager!)

    However, even if #1 or #2 is true, it doesn't have anything to do with
    TCC -- that dialog is displayed and managed by the Windows console
    manager, not TCC. (You'll get the same dialog in CMD.) TCC doesn't
    handle any mouse messages unless you've turned on ON xBUTTON.

    Rex Conn
    JP Software
     
  3. Jim Cook

    Joined:
    May 20, 2008
    Messages:
    604
    Likes Received:
    0
    Even after I disabled TCSTART and TCMD.INI and killed most processes
    in my system, it is perfectly repeatable.

    In fact, if I'm running multiple TCC.EXE stand-alone sessions at the
    same time as multiple CMD.EXE sessions, if I bring up a FIND dialog in
    any TCC or CMD session, all TCC sessions beep and all CMD sessions
    behave -- they either receive keystrokes or set the focus to the FIND
    dialog, for the one that launched it.

    If further inspection reveals anything else, I'll post it.

    --
    Jim Cook
    2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
    Next year they're Sunday.
     
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,860
    Likes Received:
    83
    Jim Cook wrote:

    CMD uses a different API for keyboard input, so it's not surprising that
    it would behave differently.

    Regardless, it's still impossible for TCC to have anything to do with
    it. Have you tried contacting Microsoft?

    Rex Conn
    JP Software
     

Share This Page