| Title: | Bugs in TPU and EVE |
| Notice: | Please read 1.* & include the version number in EVERY bug report |
| Moderator: | EDSDS6::TOWNSEND |
| Created: | Thu Mar 25 1993 |
| Last Modified: | Thu Apr 24 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2318 |
| Total number of notes: | 7869 |
This bug seems to be present up to 7.1 at least but isn't
in 5.5-2.
The following procedure demonstrates the problem. Prior to
6.1 the effect of issuing the tpu command then changing the
REQUEST buffer and exiting produced a new version of the file.
Now, if run on anything after 6.1 if the user exits, rather than
write the file out for him automatically he is asked :-
Type filename for buffer REQUEST (press RETURN to not write it):
Naturally, most users are pressing return here and so losing their
changes.
Here is the procedure and the command file to run it. You'll need
to create a couple of files in your directory; template.txt and
request.123. Then enter the tpu command user_display_help, change
the REQUEST buffer and then attempt to exit.
procedure user_display_help
top_of_window:=get_info(current_window,"visible_top");
adjust_window (current_window,+10,0);
example1_window:=create_window(top_of_window,10,off);
example2_window:=create_window(11,12,off);
example1_buffer:=create_buffer("example","help$script");
example2_buffer:=create_buffer("request","request");
map (example1_window, example1_buffer);
map (example2_window, example2_buffer);
endprocedure;
$ assign sys$disk:[]template.txt help$script
$ assign sys$disk:[]request.123 request
$ request = "''f$trnlnm("request")'"
$ define/user sys$input sys$command
$ edit/tpu/command=user_display_help.com 'request
$ exit
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2318.1 | does it have an output file? Find an EVE routine | HNDYMN::MCCARTHY | A Quinn Martin Production | Thu Apr 24 1997 09:49 | 15 |
Check the attributes of the request buffer. The way EVE runs through all buffers and what it checks for may have changed. Does "request" (ie the logical and the file) exist when this is run? I think it may have something to do with the output_file not being set on the buffer (ie it does not know what to write it out to). You may want to use an EVE procedure to create the request buffer, no I can't recommend one. You could also do a SET (OUTPUT_FILE,example2_buffer, get_info (example2_buffer,"file_name")); Brian J. | |||||
| 2318.2 | 63101::WANG | James - DECset Engineering | Thu Apr 24 1997 12:51 | 18 | |
According to TPU reference manual, if you modify a buffer that has an
associated file name ( specified a file name for the second parameter of
CREATE_BUFFR), TPU will write out a new version of the file
without querying user for file name when EXIT.
I think this is a bug in TPU but I don't know when this will be fixed
because TPU/EVE are in maintenance mode. At this time there is a
workaround for your problem. Put:
SET (OUTPUT_FILE, current_buffer, "request")
into procedure user_display_help just before endprocedure.
Brian, thanks for the hint !
-James
| |||||
| 2318.3 | Raised as TPU bug 337 | 63101::WANG | James - DECset Engineering | Thu Apr 24 1997 13:43 | 1 |
| 2318.4 | 63101::GLEASON | Daryl Gleason, DECset Engineering | Thu Apr 24 1997 14:09 | 11 | |
For Brian's benefit,
We did verify that the buffer in question ("request") did in fact have
the filename ("request.123", fully specified) associated with it, as a
result of the create_buffer statement. For some reason, that
association is being lost or ignored at exit time in versions of TPU
after V2.6.
Thought you might like to know. :-)
-- Daryl
| |||||