Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!purdue!decwrl!labrea!polya!rothberg
From: rothberg@polya.Stanford.EDU (Edward Rothberg)
Newsgroups: comp.sys.mac.programmer
Subject: A few questions about Ticks
Message-ID: <3417@polya.Stanford.EDU>
Date: 27 Jul 88 01:31:50 GMT
Organization: Stanford University
Lines: 22

I've been playing around with time dependent stuff a bit recently, and I
can't seem to find the answers to the following questions:

1)  It's made clear that Ticks will be updated whether there's time to
	do any VBL tasks or not.  What I'm wondering is, if I put
	something in the queue with a vblCount of say 60, and in
	the interval between then and 60 ticks later, it's only able to
	do VBL tasks 30 times (a gross exageration for example's sake),
	will my VBL task still be executed after 60 ticks, or will it
	be executed after 60 + the lost 30?  i.e. is decrementing the
	vblCount of all VBL tasks something that is always done, or only
	something that's done if there's time?

2)  Why use the TickCount() trap when the Global variable Ticks is available?
	I realize that the underlying philosophy is that it makes future
	compatibility more likely, but it seems to me that Ticks is a machine
	state, not a process state, and therefore there doesn't seem to be
	a great motivation to get rid of it.  Is it in Apple's list of
	"targeted" low-memory globals, globals that Apple says will have to
	go in the future?

Ed Rothberg
rothberg@polya.stanford.edu