Re: [U2] [UV] INPUTTRAP Statement

Bill Haskett <[email protected]>
Newsgroups gmane.comp.db.u2.general
Message-ID <[email protected]>
Yea.  It took me awhile to figure this out. ON.ABORT sets up a (VOC) 
entry to be run on a program abort; but only once!  If you want it to 
happen again, which I wanted in our menu system (i.e. I didn't want 
people to press [Ctrl]+C to get to TCL out of our menu system), then my 
(VOC) item "SORRY" looks like:

001  PA
002  ON.ABORT SORRY
003  MENU

...where "ON.ABORT SORRY" is activated to occur upon the next program 
abort (which a break key is an abort) and "MENU" sends the user back to 
the main menu.  When a user logs on I execute this command (and a 
UTD.OPTION 105 OFF to make sure ON.ABORT can't be executed from within 
BASIC) then route users to the main menu. Now, if anyone tries to break 
out of our menu system the abort management is activated again (awaiting 
an abort) and the user is routed to the main menu.  This is convoluted, 
but it works.  :-)

Bill

------------------------------------------------------------------------
----- Original Message -----
*From:* [email protected]
*To:* [email protected]
*Date:* 12/23/2013 1:13 PM
*Subject:* Re: [U2] [UV] INPUTTRAP Statement
> Could you explain more why your On.Abort executes another On.Abort ?
> I didn't understand that part.
>
>
>
> -----Original Message-----
> From: Bill Haskett <[email protected]>
> To: U2 Users List <[email protected]>
> Sent: Mon, Dec 23, 2013 1:06 pm
> Subject: Re: [U2] [UV] INPUTTRAP Statement
>
>
> You can't trap the 'break' key, but you can prevent its usage.  In
> UniData it is:
>
> ON.ABORT
>
> ...which is a very finicky task to accomplish in that the command
> doesn't permanently turn on or off anything, it simply executes a
> command on a program abort.  For us, the command executes the ON.ABORT
> command again (for the next abort) the routes the user back to the main
> menu; a very abstract way to get the job done.
>
> HTH,
>
> Bill
>
> ------------------------------------------------------------------------
> ----- Original Message -----
> *From:* [email protected]
> *To:* [email protected]
> *Date:* 12/23/2013 11:56 AM
> *Subject:* Re: [U2] [UV] INPUTTRAP Statement
>> I don't think you can use *any* of the chars that are pre-trapped like ctrl-c
> (Break)
>> That is, chars that actually make the op-sys wake up and act in immediate mode
>>
>>
>> If you are trying to *trap* the break so you can see when someone is trying to
> use it, there is another way, although the other way of which I'm thinking
> doesn't *prevent* its use, it just *records* its use.
>> Maybe you could go into more detail about why you're trying to trap ctrl-c
>>
>>
>>
>> -----Original Message-----
>> From: Perry Taylor <[email protected]>
>> To: U2-Users List <[email protected]>
>> Sent: Mon, Dec 23, 2013 11:41 am
>> Subject: [U2] [UV] INPUTTRAP Statement
>>
>>
>> Has anyone ever used the INPUTTRAP statement in UniVerse BASIC?  I want to be
>> able to trap a break (Ctrl-c) but I can't seem to get it to work with CHAR(3),
>> or any other character for that matter.  The UniVerse BASIC Commands
>> documentation provides no examples on its use.
>>
>> Anybody done anything like this?  Any sample code you're willing to share?
>>
>> Thanks.
>> Perry Taylor
>> Senior MV Architect
>> ZirMed
>> 888 West Market Street, Suite 400
>> Louisville, KY 40202
>> www.zirmed.com<http://www.zirmed.com/>
>>
>>
>>
>> CONFIDENTIALITY NOTICE: This e-mail message, including any
>> attachments, is for the sole use of the intended recipient(s)
>> and may contain confidential and privileged information.  Any
>> unauthorized review, use, disclosure or distribution is
>> prohibited. ZirMed, Inc. has strict policies regarding the
>> content of e-mail communications, specifically Protected Health
>> Information, any communications containing such material will
>> be returned to the originating party with such advisement
>> noted. If you are not the intended recipient, please contact
>> the sender by reply e-mail and destroy all copies of the
>> original message.
>> _______________________________________________
>> U2-Users mailing list
>> [email protected]
>> http://listserver.u2ug.org/mailman/listinfo/u2-users
>>
>>    
>> _______________________________________________
>> U2-Users mailing list
>> [email protected]
>> http://listserver.u2ug.org/mailman/listinfo/u2-users
> _______________________________________________
> U2-Users mailing list
> [email protected]
> http://listserver.u2ug.org/mailman/listinfo/u2-users
>
>   
> _______________________________________________
> U2-Users mailing list
> [email protected]
> http://listserver.u2ug.org/mailman/listinfo/u2-users

_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.