HP3000-L Archives

August 2002, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Greg Chaplin <[log in to unmask]>
Reply To:
Greg Chaplin <[log in to unmask]>
Date:
Tue, 27 Aug 2002 14:54:03 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (52 lines)
Tom,

I think that it's ok to leave that bit in there about the "hard reset". The
average user probably would bother to try to find how to do a reset
from the drop-down menus, and ctrl-R does not apply to QCTerm.
The idea is to make it _difficult_ to close QCTerm so that it is easier
and faster to log out of the application cleanly. A cluey user can kill
QCTerm regardless of whether it is in "unkillable" mode or not by using
Ctrl-Alt-Delete or otherwise with the Task List or Task Manager.

This functionality covers my requirements perfectly. A big pat on the
back to Wirt & his team at AICS. I'll be promoting QCTerm as a viable
alternative to Reflection for our external users, especially now that
it is the only emulator that uses Advanced Telnet.


------------------------------------------------------------------------------------------
Greg Chaplin                  
www.unisuper.com.au
[log in to unmask]
UniSuper                       
Level 37, 385 Bourke Street
Melbourne  VIC  3000,          
Australia.                     
Phone: 61 3 9691 4145
Fax:   61 3 9691 4141


>>> Tom Emerson <[log in to unmask]> 27/08/02 14:35:39 >>>
> -----Original Message-----
> From: Wirt Atmar
[several snippages follow...]
> The new version (Version 0.96i) is now available for download at:
> Two new escape sequences have been defined:
> If QCTerm is in the unkillable state, (i) ALT+F4, ... bring up
> an "Improper Exit Warning" box, telling the user what to do. You may
> perform a hard reset to reset QCTerm's internal "unkillable" flag.

Ummm, doesn't "perform a hard reset to reset the unkillable flag" defeat the
purpose of an unkillable flag?  Users will quickly learn that instead of
<alt-f4>/exit/whatever, they will do a <ctrl-R> first [ctrl-r is WRQ's hard
reset -- dunno what qcterm's is, but you get the point] and you're right
back where you started: users "improperly" bailing out willy-nilly leaving
the host app in an uncertain state.  Then again, perhaps this is how WRQ's
emulator works [never had the need for this "feature" -- my apps aren't that
complex]

<other bits snipped>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2