NetNews Usenet Archive 1993 #1/NN_1993_1.iso/spool/comp/sys/mac/hypercar/4703

Internet Message Format | 1993-01-04 | 1.6 KB

Path: sparky!uunet!gatech!usenet.ins.cwru.edu!agate!garnet.berkeley.edu!jstern
From: [e-mail] ()
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Help Deleting Cards
Date: 4 Jan 1993 23:12:13 GMT
Organization: University of California, Berkeley
Lines: 31
Message-ID: <[e-mail]>
References: <[e-mail]> <[e-mail]>
NNTP-Posting-Host: garnet.berkeley.edu

In article <[e-mail]> [e-mail] (Ed Allen and Avi Rappoport) writes:
>
>With corrupted stacks with a few corrupted cards, the usual answer is to
>move everything else.  Write a script that automates a big loop of copying
>and pasting cards to a new stack, but which skips the bad ones (whose
>numbers you have previously identified).  Start the script, see that it is
>going okay, and take a coffee break while it churns through your stack.
>
Actually, you don't even have to "previously identify" the bad ones.
I've found (at least with the corruptions I've had) that corrupted
cards don't "exist". The following loop works:
repeat with x = 1 to the number of cds
   if there is a cd x then
      go cd x
      domenu "copy card"
      go to stack uncorrupted
      domenu "paste card"
      go to stack corrupted
   end if
end repeat

This way you don't have to take the time to even figure out what card(s) is/are
corrupted. (You can add an "else" to the loop, so that it keeps track
of which ones were corrupted, if you need that info.)

Judy Stern
Instructional Technology Program
UC Berkeley
[e-mail]