| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3469.1 | This might help... | MINIM::BAY | Jim CNF ENTP PPASEL DECterm | Tue Oct 16 1990 13:49 | 15 |
| One way to keep it from going away would be to execute another
command procedure first, for instance COM3.COM, that says:
$ OPEN/SHARE/WRITE xxx KEEP_IT_OPEN
Then when you OPEN/SHARE and close from COM2.COM it will stay alive
(until you CLOSE KEEP_IT_OPEN).
As for the behavior of opening and closing a channel causing the window
to close, I'm not sure whether thats expected behavior or not.
If its REALLY a problem, QAR it and I'll investigate it.
Jim
|
| 3469.2 | refcnt == 0 -> delete DECTERM | VINO::MCARLETON | Reality; what a concept! | Tue Oct 16 1990 15:31 | 16 |
|
> As for the behavior of opening and closing a channel causing the window
> to close, I'm not sure whether thats expected behavior or not.
It is expected behavior. The DECterm controller assumes that once the
last channel to a DECterm window is closed, the user doesn't need the
window any more. This is also the only way for a program to get rid
of a DECterm window. I had to jump through hoops to get every last
channel closed to my DECterm window to make it go away. We need some
other way to control the DECterm windows created by DECwTermPort or
create/term so that the applications can control the windows. These
kinds of feature requests have been passed over in favor of putting
time into bug fixes that had to be done for each new version.
MJC
|
| 3469.3 | what about "/nohangup", won't that keep it around? | LEVEL::OSMAN | see HANNAH::IGLOO$:[OSMAN]ERIC.VT240 | Tue Oct 16 1990 16:54 | 13 |
|
I think this will work. First, LOG IN the DECterm (i.e.
create it as a normal DECterm).
Then, you need privileges, and you say
$ set term/permanent/nohangup
then log off it.
I think this will keep it around.
/Eric
|
| 3469.4 | | DECWIN::MESSENGER | Bob Messenger | Wed Oct 17 1990 13:56 | 9 |
| Re :.2
Once the last channel to a TW or FT device is closed, the driver (not DECterm)
deletes the device. I think you can prevent this from happening by setting
the NOHANGUP terminal characteristic. Once the device is deleted DECterm
might as well delete the window as well, since there is no way for your
application to read from it or write to it.
-- Bob
|
| 3469.5 | What do you propose? | MINIM::BAY | Jim CNF ENTP PPASEL DECterm | Wed Oct 17 1990 14:06 | 16 |
|
Re: <<< Note 3469.2 by VINO::MCARLETON "Reality; what a concept!" >>>
-< refcnt == 0 -> delete DECTERM >-
>We need some other way to control the DECterm windows created by
>DECwTermPort or create/term so that the applications can control the
>windows.
Did you have any particular mechanism in mind (for telling a DECterm to
go away)?
On second thought, don't answer here. There is a whole conference
dedicated to DECterm, so perhaps we can discuss it there, or you could
send me mail.
Jim
|