home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!darwin.sura.net!wupost!usc!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!bronze!yawei
- From: yawei@bronze.ucs.indiana.edu (Ya-Gui Wei ~{QG9p~})
- Subject: Re: screen saver routines
- Message-ID: <1992Jul25.182513.2838@bronze.ucs.indiana.edu>
- Organization: Indiana University
- References: <1992Jul25.064953.14956@news.ysu.edu>
- Date: Sat, 25 Jul 92 18:25:13 GMT
- Lines: 29
-
- >> I'm planning on incorporating a screen saver into my program.
- >>From what I gather, I'll need to hook onto 2 interrupts, 0x1C and
- >>0x09. My hook to interrupt 0x1C will increment a counter every
- >>time it is called and if the counter is greater than a certain
- >>amount of time, blank the screen. My hook to interrupt 0x09 will
- >>unblank the screen and clear the counter if the screen is already
- >>blanked, otherwise it will just clear the counter. Can someone
- >>tell me if this will work or have any suggestions/improvements?
-
- This is neccessary only if you are writing a TSR (memory resident
- program) or want the screen saver to act as a TSR. If you are not
- writing a TSR it is not neccessary (and not nice) to hook the
- interrupts.
-
- Instead, write a routine in your program that gets called
- periodically (e.g., a keyboard input routine.) Inside this
- routine, keep a counter of some sort, and clear the screen when
- the counter exceeded a certain value. After that you just wait
- for a keystroke then restore the screen. If precise timeing is
- required you can use the neccessary function calls in the language
- to determine the time before clearing the screen.
-
- Note that it is not a good idea for a screen saver routine to
- completely blank the screen. A better idea is to write a message
- on screen indicating what happened, and rewrite this message on
- different locations periodically.
-
- Ya-Gui Wei
-
-