[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:	DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:	See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:	STAR::VATNE

Created:	Mon Oct 30 1989
Last Modified:	Mon Dec 31 1990
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3726
Total number of notes:	19516

2631.0. "Mouse stopped since upgrading" by UTRTSC::CAHILL () Thu Apr 19 1990 05:56

    Also posted in decwindows_programming notes file.
    
I have a customer experiencing the following problem;

The problem has only appeared since upgrading to VMS 5.3,
everything worked OK on 5.1 and 5.2.

The customer has an application running in a DECterm window
which requests fields.He would normally point to a field and
click with the mouse,the fields correspond to functions keys
f7 thru f14.
He gets no response from the mouse,he can however use the function
keys without a problem.  
Also he could type information before eg. a filename.If he does 
this now the first char is displayed as something like
[-0.1,958.1].

I know there is not too much info here, unfortunatly the code 
was written in the states by my customers head office (we are
in Holland),but I have asked him to request a copy of the source,

My questions are:-

1. any idea why the mouse should stop working since the upgrade ?

2. any idea why  he gets [-0.1,958.1] ?


all input appreciated..tks

GC.

T.R Title User Personal
Name Date Lines

2631.1 ReGIS locator reports HANNAH::MESSENGER Bob Messenger Thu Apr 19 1990 11:58 33

T.R	Title	User	Personal Name	Date	Lines
2631.1	ReGIS locator reports	HANNAH::MESSENGER	Bob Messenger	`Thu Apr 19 1990 11:58`	33
	Re: .0 It sounds like this software is using ReGIS locator input. There were several bugs in the ReGIS locator input support in VMS V5.1 and V5.2 which I fixed in VMS V5.3, and it's possible that the customer's software relies on one or more of these bugs. Does the software work on a VT330/VT340? >The customer has an application running in a DECterm window >which requests fields.He would normally point to a field and click with the mouse,the fields correspond to functions keys >f7 thru f14. >He gets no response from the mouse,he can however use the function >keys without a problem. >Also he could type information before eg. a filename.If he does >this now the first char is displayed as something like >[-0.1,958.1]. [-0.1,958.1] looks very much like part of a ReGIS locator report. By default, the report would start with an escape sequence, followed by the bracketed coordinates and a carriage return. What might have happened was that the application tried to read the function key/mouse report, and this read was terminated by the escape sequence, leaving [-0.1,958.1] in the typeahead buffer. Then when the user tried to enter the file name, the application saw [-0.1,958.1]. If this is what's happening, you should be able to enter a file name by typing ^X (to clear the typeahead buffer) followed by the file name. One thing to look at is whether the terminal is set up as SET TERM/ESCAPE or SET TERM/NOESCAPE. This would affect how the application reads escape sequences. Maybe it was set one way before the upgrade and the other way after the upgrade. -- Bob

Re: .0

It sounds like this software is using ReGIS locator input.  There were several
bugs in the ReGIS locator input support in VMS V5.1 and V5.2 which I fixed in
VMS V5.3, and it's possible that the customer's software relies on one or more
of these bugs.  Does the software work on a VT330/VT340?

>The customer has an application running in a DECterm window
>which requests fields.He would normally point to a field and
click with the mouse,the fields correspond to functions keys
>f7 thru f14.
>He gets no response from the mouse,he can however use the function
>keys without a problem.  
>Also he could type information before eg. a filename.If he does 
>this now the first char is displayed as something like
>[-0.1,958.1].

[-0.1,958.1] looks very much like part of a ReGIS locator report.  By default,
the report would start with an escape sequence, followed by the bracketed
coordinates and a carriage return.  What might have happened was that the
application tried to read the function key/mouse report, and this read was
terminated by the escape sequence, leaving [-0.1,958.1] in the typeahead
buffer.  Then when the user tried to enter the file name, the application saw
[-0.1,958.1].  If this is what's happening, you should be able to enter a
file name by typing ^X (to clear the typeahead buffer) followed by the file
name.

One thing to look at is whether the terminal is set up as SET TERM/ESCAPE
or SET TERM/NOESCAPE.  This would affect how the application reads escape
sequences.  Maybe it was set one way before the upgrade and the other way
after the upgrade.

				-- Bob