[A83] Re: homescreen cursor location when ! is closed
[Prev][Next][Index][Thread]
[A83] Re: homescreen cursor location when ! is closed
Thanks... It was cmdcursor i was looking for
At Friday, 27 July 2001, you wrote:
>cmdCursor is probably what you're looking for. It's 16-bit, and
should hold
>the offset into the buffer that the cursor was at.
>
>Hope this helps,
>-Dan Englender
>
>----- Original Message -----
>From: <Jkhum98@aol.com>
>To: <assembly-83@lists.ticalc.org>
>Sent: Friday, July 27, 2001 5:20 PM
>Subject: [A83] Re: homescreen cursor location when ! is closed
>
>> The "location of the homescreen cursor" doesnt specifically coincide
with
>> these edit memory locations, but instead an edit session uses
them to keep
>> track of boundaries of the variable open for editing and the cursor
>location
>> within the edit buffer. Homescreen input is one form of this edit
session
>> where the typed tokens go into the ! variable for temporary storage
before
>it
>> is parsed. As for the memory locations of where the screen and cursor
>> position info is stored when an app or another context is run,
I would
>guess
>> Command Shadow, but I'm not certain. Why do you need to know this
>> information? Perhaps a more knowledgable person of the topic will
give his
>> insight when he gets to his Email sometime today. :)
>>
>> -Jason Kovacs
>>
>>
>> In a message dated 7/27/01 2:22:09 PM Central Daylight Time,
>> hochhaus@cmh2000.com writes:
>>
>> > Does anyone know where the location of the homescreen cursor (how
>> > far into the edited equation the cursor is) is stored when ! is not
>> > currently being edited. Normally (when ! is "open" for editing) you
>> > can determine the location of cursor by looking at these memory
>locations:
>> >
>> > editTop EQU 96F4h
>> > editCursor EQU 96F6h
>> > editTail EQU 96F8h
>> > editBtm EQU 96FAh
>> >
>> > However when you run a program (or enter an APP) the homescreen
edit
>> > closes. Then these memory locations no longer represent the
homescreen
>> > cursor location. Any ideas?
>> >
>> > Thanks,
>> > -Andy Hochhaus
>>
>>
>>
>>
>>
>