MaxCoderz

This is why:

GetCSCHook: .db $83 cp $1b ret nz di exx ld a,(Counter-$9d95+AppBackUpScreen) or a jp m,SetNormalKey-$9d95+AppBackUpScreen dec a ld (Counter-$9d95+AppBackUpScreen),a ld h,0 ld l,a ld de,OrderOfKeys-$9d95+AppBackUpScreen add hl,de ld a,(hl) or a exx ei ret SetNormalKey: ld a,b or a jr z,NoKeyPressed...

I'm trying to make the GetCSC hook record a keypress if a keypress is detected, but exit if no keypress is detected. It may seem easy, but I think it's a bit harder than it seems. Once in A=$1b mode, a ld a,b and then or a can easily determine whether there was a keypress. However, such code makes t...

You mean rewrite the code at $0038 so that when it runs in IM 1 it calls whatever you want to? It's a bit impractical, since TI as pretty much stuffed that area full of code and there's no saferam there.

It sort of makes TSRs not worth programming...

I think TI-BASIC requires the calc's interrupts and only the calc's interrupts to run correctly. Many menus and functions of the TI-OS are inaccessible when you run IM 2, for example, when I run my own TSR, and then try to graph something, it gives me an ERR:SYNTAX or something and then destroys the...

To return a nz condition before exiting.

A simple keyhook? How can I still have it run in the background while the TI-OS is running?

I only want it to move when left/right are pressed, along with a few different actions by pressing other keys. But other than that, it should stay in one place without pressing keys.

I want to program a small piece of code that displays a sprite on the homescreen (or any other screen that doesn't use IM 1). I could also want it to move around. The thing is, I've been working with TSRs, but people have found it to be difficult to work with. They suggested hooks, but I don't know ...

Yeah, that's what I meant, although I feel it needs to be more dynamic for editing and parsing. I like the idea for a base code which I will try to expand around.

Timendus wrote:Sounds like a very good idea, but I fear there will be some limitation keeping you from using that much tokens

Well, I still don't know how to go about making tokens, much less know about what limitations will keep me away from making that many.

Not for every command, but for every instruction and flag and some other ti83plus.inc equates. I think registers would also have a token associated with it, and the combination of an instruction, register, or a memory destination would be replaced with the appropriate hex or binary code.

I want to make the assembler/editor have tokens, which would increase ease of programming (instead of typing on the awkward "keyboard" on the calc). It would be similar to TI-BASIC tokens, but I don't know how to "define" tokens.

But still, is it possible to make your own tokens like Omnicalc etc?