Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!hp-pcd!hpcvra.cv.hp.com!rnews!hpcvbbs!akcs.falco
From: akcs.falco@hpcvbbs.UUCP (Andrey Dolgachev)
Newsgroups: comp.sys.handhelds
Subject: Re: Minehunt II turbo (an HP48 game)
Message-ID: <282068b7:2986.2comp.sys.handhelds;1@hpcvbbs.UUCP>
Date: 2 May 91 19:40:16 GMT
References: <11665@mentor.cc.purdue.edu> <1991May1.012924.15286@umbc3.umbc.edu>
Lines: 51

Lines: 49

First of all, to answer Rouben's question, the ASC file of Minehunt II is
26k large.  This means that you need 52k of RAM free on your calculator
to d/l it.  After you convert it to binary, the file is "only" 13k.  I
think that it would be nice if some kind soul, or the original author
himself, would post the program in UUencoded form.

Secondly, to the original author.  Minehunt is a cool program, but I do
have a few suggestions.  First and most importantly, it is not a good ide
idea to use the following to put a graphic up on the screen:
   graphic
   PICT
   STO

It is also not a good idea to use PICT PURGE.  Anytime that you directly
manipulate the PICT like a normal variable, WHILE the PICT is being
displayed with the use of PB
(gar!, where was I)  -with the use of PVIEW, the screen does that
annoying static thing.  This is especially evident in your HELP program,
where every screen gets that static look in between screens.  I am
guessing that you did not want that look on purpose, since it isn't
exactly cool looking.  Anyways, instead of using the PICT as a variable
like you did, use REPL and ERASE.  In other words, if you want to erase
the screen, don't use PICT PURGE but simply ERASE.  If you want to put a
graphic up on the screen, do the following:

    PICT
    { #0d #0d }
    graphic
     REPL

That will do the same thing, and the next screen is shown faster and w/o
the static look.  Additionally, the REPL command doesn't need to have as
much free memory as the PICT STO command (with a large GROB).

The other thing I wanted to mention was that instead of using DO UNTIL
KEY END DROP to wait for a key press, simply use 0 WAIT DROP.  This saves
a little memory (O.K>, very little) but more importantly, it uses less
battery power.  If you notice, when you use a DO UNTIL loop, the little
hourglass annunciator turns on and stays on.  If you leave the calculator
on and leave, the calculator wil not turn off and just keeps doing the
loop over and over.  On the other hand, if you use the O WAIT, the
annunciator does not go on, the calculator doesn't use as much power, and
it will turn itself off.  It's a minor point, but it's a good idea, just
in case someone leaves the calculator on one of the HELP screens.

Otherwise, it's a cool program, and the graphics are great, a great
improvement in terms of looks compared tot he original.

        ---Falco