Re: A85: x-stat and delete protection
[Prev][Next][Index][Thread]
Re: A85: x-stat and delete protection
I could make a TSR that waits until the delete menu item is on the screen,
then blocks it out before it becomes useable. I did something similiar
once by adding a shell's custom menu entry to every menu on the calc (as
long as the 5th entry was blank). You could also make it so it could block
any menu item, xmit or recv under the link menu...
If you want I could code it. It would be fairly simple.
At 01:27 AM 3/5/99 -0500, you wrote:
>
>Only one problem with this current thread: the original question seems to
>have been forgotten.
>
>amaya@alaska.net had asked if vars could simply be non-deletable... but
>still accessible as a normal variable...
>
>My idea would be to somehow change the calculator so that when
>2nd|mem|delete is chosen, a jump to a new bit of code could happen... then,
>it would be possible to code a delete utility which maintains a table of
>variable attributes (no-delete is the only one I can think of)
>
>This way, the utility can check the table to see if a variable can be
>deleted before the deletion is done...
>
>I'm sure that there are TI-85 hackers on this list who actually have time to
>implement this, as I do not... I think it would be a very useful utility...
>
>(Installation isn't hard - make an install program which deletes itself)
>
>Ok, I'm sorry if this message lacks a lot of coherency, I need to get
>sleep...
>
>...Trevor
>
>
>----- Original Message -----
>>you are correct. ive done this a couple times. i like to use &name, jsut
>>for usgard similartiy, although it means nothing similar at all, so it
>>doesnt really matter :)
>>
>>kaus
>
>
>
>
>
References: