jmccarty@ucsd.edu (Jon McCarty) (09/26/90)
I'm not a hypercard expert, but it looks like I have a blown stack @8^o At one card (#13), the "next" button stops working. I can use "find" to get to card (#14), but then the "previous" button doesn't work. I can't delete card #13 at all. "Compress Stack" also reports a "disk error -24" on my mac+ and "Can't compress Stack" on a Mac SE/30. Hypercard versions 1.2.5. and 1.2.1, resp. my guess is that stacks are some kind of doubly linked lists, and my pointers are screwed up; but like I said, I'm no expert. Does anyone know how to fix this? I tried a sort command, and it did work, but didn't help. As they say in Iraq, tanks in advance! -- Jon Internet: jmccarty@ucsd.edu bitnet : jmccarty@ucsd
pease@amarna.gsfc.nasa.gov (Pease) (09/26/90)
In article <2982@network.ucsd.edu>, jmccarty@ucsd.edu (Jon McCarty) writes... >I'm not a hypercard expert, but it looks like I have a blown stack @8^o >At one card (#13), the "next" button stops working. I can use "find" to >get to card (#14), but then the "previous" button doesn't work. I can't >delete card #13 at all. "Compress Stack" also reports a "disk error >-24" on my mac+ and "Can't compress Stack" on a Mac SE/30. Hypercard >versions 1.2.5. and 1.2.1, resp. > I had this happen to me once also. I "fixed" my problem by creating a New Stack (with same background as the problem stack), then wrote a button script which went to the problem stack, cut card, back to last card of new stack, and paste card. In my case, the stack had a field "name" which I checked to see if I was at the card before the problem card, and I quit on that card. I then modified the script to start at the card after the bad card and proceeded to copy the remainder of the cards. This is how I managed to delete the bad card. Phil Pease My witty disclaimer - everything I perceive, through either sensory or extrasensory means, has been filtered to such an extent that you had better not attempt to attribute anything I say to anyone else.