Re: A86: state flags

To: assembly-86@lists.ticalc.org
Subject: Re: A86: state flags
From: Joshua J Seagoe <rabidcow@juno.com>
Date: Mon, 8 Nov 1999 09:13:25 -0800
Reply-To: assembly-86@lists.ticalc.org

changing _CXCURAPP would not actually change what the current running
application is, it's only there for a quick way to figure it out.  if you
actually wanted to change state, you would need to change the six _cx...
pointers and the context state flags under (iy+something), for most apps,
there are rom calls to set them up (at least partially)
technically, i wouldn't really call _CXCURAPP a flag, it's a byte sized
variable identifying the current application context.  (blah, blah,
blah...)

-josh

On Mon, 08 Nov 1999 06:55:37 -0800 Cassady Roop <croop@oregontrail.net>
writes:
>
>so those state flags, like _CXCURAPP, tell the calc where it is...
>
>Does that have values corresponding to apps like the PRGM menu and 
>the
>POLY, SIMULT, and others?  If I loaded, say, the value for the PRGM 
>menu
>to this location, and then exited my program, would the PRGM menu be
>brought up?  Also, if it were already in the prgm menu, and I loaded 
>a
>different value, like the homescreen, each time the user tried to go 
>to
>the program menu, would it seem to them like the PRGM button had 
>stopped
>working?
>
>Cassady Roop
>

___________________________________________________________________
Get the Internet just the way you want it.
Free software, free e-mail, and free Internet access for a month!
Try Juno Web: http://dl.www.juno.com/dynoget/tagj.

Follow-Ups:

Re: A86: state flags

From: Cassady Roop <croop@oregontrail.net>