Re: A86: call _getky usage...


[Prev][Next][Index][Thread]

Re: A86: call _getky usage...




Keep in mind that _getkey and _getky uses different equates. One routine
uses the equates defined in #ti86asm.inc, the other uses the equates defined
in the User manual. I dont recall which is which; however just see TI's
documentation on their web site

Later,
 Matt


>Ok, i think i fixed the things you said were wrong, but the problem left is
>either getky isn't detecting keys (i'm using an emulator, easier but
>probably less reliable than the calculator, its called Ti86emu.exe) or
getky
>is detecting but i'm not using it right. Also, i see the screen refresh,
and
>i think i'm using too many calls or jp's which may slow it down... help me
>fix this so i can see what a working asm looks like.
>
>Alan Wong / Damnation
>
>Asm is attached...
>
>-----Original Message-----
>From: Dux Gregis <assets@eden.rutgers.edu>
>To: assembly-86@lists.ticalc.org <assembly-86@lists.ticalc.org>
>Date: Wednesday, July 22, 1998 1:08 AM
>Subject: Re: A86: call _getky usage...(AAAHHHGGG)
>
>
>>
>>
>>
>>Roy Wong wrote:
>>
>>> Ok, i'm going to calmly say this, but i think i'm cursed. Everything i
>try
>>> to do in the program never seems to work, and even after you guys try to
>>> help me, it still doesn't work... I don't know what to do!
>>> Here is the source for the start of something, all i'm trying to do is
>get
>>> the mouse to move using only _getky. In the game, i won't have a mouse,
i
>>> just want to know that i can make a mouse move, so that i know i can
feed
>>> commands in and have a reaction happen. But the mouse is not moving
>(mouse
>>> pointer thing that is)....
>>>
>>> The asm is attached...
>>>
>>> Thanks for all your help, and sooner or later i should get the hang of
>it...
>>>
>>> Alan Wong / Damnation
>>>
>>
>>First, you call something named SpriteMove that never returns.  Then you
>push bc alot
>>without ever popping it again.  bc is never destroyed; you don't need to
>push it at
>>all.  It won't be long :-)
>>
>>
>


Follow-Ups: