Bug 60121 - xterm does not accept input when pointer in scroll bar
Summary: xterm does not accept input when pointer in scroll bar
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-20 16:19 UTC by Need Real Name
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-03-01 10:00:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2002-02-20 16:19:03 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:

When an xterm with a scroll bar is used, and the mouse pointer is in 
the scroll bar, the xterm does not accept keyboard input. This used
to work.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Start an xterm with a scroll bar using  "xterm -sb"
2. Ensure that it has the input focus
2. Move the mouse pointer so that it's pointing to the scroll bar
3. Type some characters.	

Actual Results:  The characters are not typed into the xterm (it acts as if 
nothing
was typed).


Expected Results:  The characters should have been entered just as they would 
if the
pointer was anywhere else (as always used to happen :)

Additional info:


Using XFree86-4.1.0-15 but the problem exists in RH7.2 with no errata RPMs 
applied.

Comment 1 Mike A. Harris 2002-02-22 03:11:12 UTC
In the XTerm.ad resources file, there is a line VT100*translations
Change the * to a . or vice versa.  Restart XFree86 and let me know
if the problem goes away.

Comment 2 Need Real Name 2002-03-01 10:00:21 UTC
Thanks for looking into this!

I assume you mean the file
   "/usr/X11R6/lib/X11/app-defaults/XTerm"

I've edited it to change *both* the lines starting
   *VT100*translations:
to
   *VT100.translations:
This has fixed the problem - many thanks!

Patrick



Note You need to log in before you can comment on or make changes to this bug.