paryavi@harris.cis.ksu.edu (Saiid Paryavi) (01/23/89)
Is there an easy and quick way to merge two stacks with the same type of
cards into one stack.
Thanks in advance
***/\/\****/\/\******/\/\****/\* Saiid Paryavi
**/*/\*\**/*/\*\****/*/\*\**/*/* paryavi@ksuvax1.cis.ksu.edu
*/*/**\*\/*/**\*\**/*/**\*\/*/** paryavi@ksuvax1.BITNET
*\/****\/\/****\*\/\/****\/\/*** {pyramid,ucsd}!ncr-sd!ncrwic!ksuvax1!paryaviannie@cs.swarthmore.edu (Annie Fetter) (01/24/89)
In article <534@deimos.cis.ksu.edu> paryavi@harris.cis.ksu.edu (Saiid Paryavi) writes: > Is there an easy and quick way to merge two stacks with the same type of > cards into one stack. > I am not aware of any "easy" way to do this in Hypercard, but you could define a key stroke in QuickKeys within the Hypercard domain that would do it for you -it would still be tedious, but it could be worse. I haven't used QuickKeys in a while, but this should be about right. First, create a button in each stack which sends you to the other stack. These two buttons would have to be background buttons _and be exactly the same_ so that Hypercard thinks the backgrounds are still the same (refer to recent discussion on this topic. Create the button in one stack, then copy and paste itinto the other one, so that their placement, name, etc, is the same. Then define a QuickKeys routine which would: 1) do menu command "Cut Card" 2) Do a mouse click on your 'to other stack' button. 3) do menu command "Paste Card" 4) mouse click on button to go back to the first stack. Put them all together in a sequence, and then go through the stack. -- Annie Fetter | annie@cs.swarthmore.edu | VGP-Department of Mathematics | fetter@swarthmr.bitnet | Swarthmore College | ...!rutgers!bpa!swatsun!annie | Swarthmore, PA 19081 | (215) 328-8225 |
hendrik@kunivv1.uucp (Kees van Eekelen) (01/26/89)
L.S. I was wondering if someone has a simple way of splitting up a large stack (literature references) into 2 or more smaller ones. A friend of mine tried it the simple way: make a new stack and copy cards, one by one. Not only is this a tedious way to handle things, but also a nasty, undocumented, problem arose: the background of the copied card was also copied,EVERY TIME, so that the new stack was double as fat as it should be. Solutions anyone? Kees van Eekelen, University of Nijmegen, Holland.