CAUSE OF CRASH - was not the group items at all

[Bill]

    I was able to duplicate the cause of the crash. I have a stack with
cards that are the size of 8.5 by 11 pieces of paper because I use them to
make forms for printing. My laptop monitor cannot hold the whole size of the
page so information in a graphic and fields on that graphic go below the
edge of the stack even though the stack does not go below that area.
Everything works. It receives data and prints ok even though some of the
fields and part of the graphic are past the bottom edge of the card.

(I have to resize the card occasionally to work on the graphic and fields at
the bottom but there is no way to add scroll bars to the stack as far as I
can tell and the old hypercard system of scrolling to the bottom of off
monitor stack windows doesn't work either and if I quit and re-start the
stack it always resets to a size that fits in the monitor window.) Perhaps I
should write a handler that makes the stack full size and repositions it
whenever I need to see the fields and graphic that are off the bottom edge.

Anyway -- the cause of crash -- There are 100 fields on the card and 20 of
them are off the bottom edge. I choose select all, copy all, make a new
card, go to that card and then everything freezes (there is no spinning
beach ball and no indication that the program has not crashed). If you wait
like 10 minutes the freeze goes away but then if you choose paste, nothing
pastes. So I try copying just 10 of the fields, one of which is off the
bottom edge. When I do this -- it takes a very long time to go to the next
card and the paste works although the field that was off the edge of the
card pastes into the middle of the card.



On 6/15/04 7:53 AM, "use-revolution-request at lists.runrev.com"
<use-revolution-request at lists.runrev.com> wrote:

>> I will be better able to document this crash (which caused me to lose 6
>> hours of programming which by the way, coming from HyperCard, is something
>> that would never happen in HyperCard) when, if, I ever understand the
>> "group" property.