home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!bnr.co.uk!uknet!yorkohm!minster!mjl-b
- From: mjl-b@minster.york.ac.uk
- Newsgroups: comp.sys.atari.st.tech
- Subject: What is user activity?
- Message-ID: <726852019.7184@minster.york.ac.uk>
- Date: 12 Jan 93 15:20:20 GMT
- Organization: Department of Computer Science, University of York, England
- Lines: 32
-
- Having posted my screen blanker to c.b.a.st and the Atari archive, I got
- some new feedback about it and screen blankers in general.
-
- As well as pointing out bugs, the problem of detecting user activity was
- raised. My screen blanker detects user activity in two ways.
-
- It hooks in an IKBD interrupt handler and hence detects key depression (and
- release) and mouse movements. It also has a hook into the BIOS trap, so that
- any output via the BIOS bcon*() routines is regarded as "activity" --
- something is happening.
-
- The problem comes with those programs that install their own IKBD handler
- and that also do not do any BIOS output. There aren't many of these programs
- around, but it would be nice to have a consistent way of detecting user
- activity that worked with everything.
-
- Jwahar Bammi suggested watching for VDI blits (i.e. calls to vro_copyfm). I
- don't like this because an additional GEM/AES handler will make the already
- slow VDI and AES even slower. I also have a gut feeling that there may be
- programs out there that blit stuff around even when nothing's happening.
- There's also the problem of those programs that use their own blit code for
- speed (such as Tempus and That's Write).
-
- So, what do people think are good ways of detecting user activity? What
- about multiple applications under MultiTOS? Is watching for blit operations
- a good idea?
-
- Mat
-
- | Mathew Lodge | "What think you, my lord, of... Love?" |
- | mjl-b@minster.york.ac.uk | "You mean rumpy-pumpy?" |
- | Langwith College, Uni of York, UK | -- Blackadder II |
-