LZ: RE: Just a small suggestion to ALL ZS programmers

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

LZ: RE: Just a small suggestion to ALL ZS programmers

UGH! ZShell needs an interrupt manager and soon! Make it like UM, so you can 
graph. Have it keep a registry of interrupt handlers (maybe actual code, maybe 
addresses) and on what interrupt-causing occurances should they be activated. 
That way, you could have more than one "interrupt handler" active at a time 
from ZShell, and they would not need GRAPH_MEM. If this isn't put into ZShell, 
Whoever wrote UM should make this.
THIS WOULD SOLVE COUNTLESS PROBLEMS! Such as an automatic switch for turboed 
calcs (everytime you ran zshell, it would delay, and it would stop as soon as 
you quit), a non-crashable screen capture program, a program to put your name 
on the home screen in grey as a background, a program like UM that wouldn't 
require erasing your mem, and they could all be running at once!


Just a suggestion


--MZB


----------
From: 	owner-list-zshell@lists.ticalc.org on behalf of Ryan Myers
Sent: 	Monday, September 02, 1996 5:26 PM
To: 	list-zshell@lists.ticalc.org
Subject: 	LZ: Just a small suggestion to ALL ZS programmers


To those who have tried to get screen shots for their games on www pages or
other things... you probably know of the utility Screen Capture 2.0.  This
is a great utility and the authors are to be commended... but unfortunately
the program cannot operate if graphics memory is altered directly... that
puts out a lot of stuff, and anything using NASR ( DOH! )


I would suggest that all ZS programmers place a screen-capture handler
inside their programs, possibly inside a resume-game-after-pause loop.
Possibly dumping the screen mem to a string and setting an internal flag,
then sending the string back into graph-mem before dropping back to ZShell...


Thanks to everyone for listening to my rant :),
Ryan Myers ( rmyers@teleport.com )
http://www.teleport.com/~rmyers/
"Canthus" on DARKWORLD


C> Warning: REALITY.SYS may be corrupt.  Reboot universe(y/n)?
Follow-Ups: