chh9@quads.uchicago.edu (Conrad Halton Halling) (08/29/90)
I got flamed a little [it barely singed my hair :-) ] because
1) I'm posting bugs that have been discussed previously and
2) I'm way past the window for bug fixes in HyperCard 1.2.5.
Well, these bugs are new to ME, and I haven't seen any discussion of them
on this forum (which I've been reading for two months, when I began a
multi-stack project). I'm using Danny Goodman's _The Complete HyperCard
Handbook_, 2nd ed., and he doesn't discuss any of these bugs. Maybe
they're in other books, but why buy them when 2.0 will be out soon?
I know bug fixes are still being made in HyperCard 2.0, so I'm posting
these bugs so that the beta-testers of 2.0 can be sure they're truly
gone. I haven't been privileged to be a beta-tester for 2.0, so I can't
see for myself. If anyone has a comprehensive list of bugs in 1.2.5,
please send them to me. (For example, what is the "card ten" bug?)
Two more things in 1.2.5 that I'd like to be missing in 2.0:
o In HyperCard 1.2, the "topLeft" property coordinates are reported in
the order Left, Top. Similarly, the "bottomRight" property coordinates
are reported in the order Right, Bottom. So the more logical names for
these properties would have been "leftTop" and "rightBottom". Will
this be changed in HyperCard 2.0? (I know, it's probably too late,
due to precedent, but this is the best opportunity. You could
leave the topLeft and bottomRight properties, but add the leftTop
and rightBottom properties, which would report the same values.)
o Make a new stack. Create a button and set the script to:
on mouseUp
ask "Change name of stack to:"
if it is not empty then
set name of this stack to it
put name of this stack -- bug here; HyperCard looks for the
end if -- stack under its old name
end mouseUp
OK, that's it -- I'm out of complaints! One of the things I like about
this forum is that people from Apple read it -- it makes us feel like
we have some real input.
Signed, a hapless HyperCard hacker.
--
Conrad Halling
chh9@midway.uchicago.eduthom@dewey.soe.berkeley.edu (Thom Gillespie) (08/29/90)
In article <1990Aug28.214702.7520@midway.uchicago.edu> chh9@quads.uchicago.edu (Conrad Halton Halling) writes: >I got flamed a little [it barely singed my hair :-) ] because > 1) I'm posting bugs that have been discussed previously and > 2) I'm way past the window for bug fixes in HyperCard 1.2.5. > >Well, these bugs are new to ME, and I haven't seen any discussion of them >on this forum (which I've been reading for two months, when I began a >multi-stack project). I'm using Danny Goodman's _The Complete HyperCard >-- ... >Conrad Halling I think a listing would be more useful than a posting of individual bugs. Some thing a little warmer than tech notes. A simple stack of bugs and then users can post their kludges around them. Individual postings tend to get missed. Something quarterly would be nice. Another thought-> I think the 2nd edition of the Shaffer book had some info which was posted. I thought this was a nice touch. So far HyperCard is a little different than other updates to software. Since the latest version runs on all machines, few people have any reason to sit with 1.2.1, they will go to 2.0. I have ALOT of old HyperCard books from past versions. I hate to think of parting with my HyperCard Bible from Waite but it is badly out of date and from what I've heard they have no plans to update for 2.0 -- I can't figure out why. Their book is excellent, it just needs some new info. --Thom
JS05STAF@MIAMIU.BITNET (Joe Simpson) (08/30/90)
The Apple Bug Reporter stack would be a great way to keep track of bugs. Easy to transfer info in/out. Easy powerfull search.