A86: Re: Event-trapping was: stop
[Prev][Next][Index][Thread]
A86: Re: Event-trapping was: stop
On Tue, 10 Mar 1998 03:04:43 -0500 Dux Gregis <assets@eden.rutgers.edu>
writes:
>Klukan wrote:
>> Dux Gregis wrote:
>> Can you send me some sample code on how to use all this to lock and
>> unlock the memory?
>Put your code in [sqrt]KEY and set the flag to lock it, reset the flag
>to
>unlock it.The code shold start with a call to $479f (?). Then check
>for
>calc states and use ret if you want the state to be inactive or under
>special conditions.
Ok, so what do I do if I don't want to trap the event but want it to
continue as normal?
>(I think that $479f sets up the calc to skip over
>certain OS behaviors).
>This isn't exactly right. But it's probably on the right track. I'll
>work on it. ;-)
>
>With the [sqrt]PARSE it seems like calc functions can be disabled.
>For
>added memory protection, Rascall (or your shell) should disable
>"Delvar(",
>so as to prevent the deletion of all varaibles, especially TI-85
>strings.
>
>> I'm guessing that I set the flags and make the
>> call.
>
>No, set the flag and it's like an interrupt.
>
>> How are the (sqrt)KEY and similar programs created?
>
>using _CREATEPROGlook at the include files
>
>> Also, does
>> anyone have info on _CXCURAPP? Thanks.
>>
>> -Jeremy
>
>
>
>
_____________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]
References: