Related to:
> The only downside is that you'll have to put a % after the rect fields:-
> gWorldRects.top%(3)  gWorldRects.bottom%(3)  etc
> to avoid compiler warning messsages, whereas with a true RECT record you
> can omit the %.

I have noticed that while that is true of RECT records, it isn't true of
POINT ones: I've found that if you DIM mousept AS POINT, then the compiler
rejects things like:
  y = mousept.v
but is happy with
  y = mousept.v%

... Yet xrect.top for example works fine and you don't need to do xrec.top%.

Associated with this are 2 curious things:

(1) while RECT is defined in Tlbx Standard.Incl, I can find no similar
definition of the POINT record (yet it works!)

(2) In Tlbx QuickTime.Incl there is this definition:
BEGIN RECORD TimeRecord
  DIM top as short
  dim left as short
  dim bottom as short
  dim right as short
END RECORD

I was wondering if that was an error, as they seem like funny field names
for a "time record"...

-- 
Robin
====================================================
Genesearch Pty Ltd
E-mail: robinc@...
WWW:    http://www.genesearch.com.au
====================================================