Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!jkc
From: jkc@Apple.COM (John Kevin Calhoun)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: HyperCard 2.1
Keywords: HyperCard 2.1, Picture XCMD, changes
Message-ID: <53797@apple.Apple.COM>
Date: 8 Jun 91 22:38:41 GMT
References: <5442@network.ucsd.edu>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 32


In article <5442@network.ucsd.edu> bjustin@network.ucsd.edu (BIll Justin)
writes:
>Just received word from a very reliable source that there are some
>significant changes in HyperCard 2.1 versus HyperCard 2.0v2.
>Specifically, I was told the Picture XCMD was done differently, and
>so behaves differently than described in Goodman and other manuals.

I've been hearing this rumor persistently over the last several days.
I wonder if your source can supply more information -- whichever
"significant change" in 2.1 is causing a problem, it's certainly not
in the Picture XCMD.  There were only two changes to Picture for 2.1. 

  1) a bug fix: after the mouseDownInPicture message is sent,
     the mouseUpInPicture message is sent only if the mouse is
     still over the picture.
  2) a minor enhancement: Picture now accepts a sixth parameter,
     to tell it whether a window should float.  This allows
     developers to create floating Picture windows with custom WDEFs.

There was no change that altered the fundamental way that it works.

Goodman's description of the Picture XCMD is still current.  You
should be aware that the description in Winkler and Kamins is
inaccurate, both for 2.0 and 2.1.

I'd like it if someone could send me a script that broke in 2.1 and
whose "breakage" is attributed to Picture, so that we can get to the
nub of the problem.

Kevin Calhoun
jkc@apple.com