Hi Dave,

Could you post a copy of your stack in RevOnline or email it to me off-list? I have never come across a problem like this before, so would be interested to see if I could work out what causes it.

Have a Stack that used to comtain:

GroupX                   (layer order)
  Graphic rect BoundingRect
  Graphic rect G-1111
  Graphic rect G-1112  etc.

The rectangles G-xxxx are all contained within BoundingRect.

I then added two buttons to the stack.

Ungrouped "GroupX" made the bounding rect smalled but shifting the bottom so it was shorter, moved the buttons to within the Rect of GroupX, regrouped and saved the Stack. Then the Group looked like this:
Why did you un-group & then re-group? If it was just to add the new buttons, you don't have to do it that way. You can either select the group, click "Edit group" in the toolbar and then create your buttons directly into the group, or you can create the buttons, cut them and then select the group and right-click to get the menu that allows you to paste into a group.

GroupX (layer order) Button "new" Button "delete" Graphic rect BoundingRect Graphic rect G-1111 Graphic rect G-1112 etc.

All seemed fine.

Then I discover that some code doesn't work anymore! On further investigation the preOpenStack and openStack handlers are not being called. I then editing the card script to beep if openStack is entered and put a breakpoint on the beep and hey presto I hit the breakpoint and now everything works fine!
It may be that un-grouping & re-grouping messed with the message passing hierarchy. That's about all I can think of for this one.

I close the stack, shutdown RunRev and re-load the stack. Now "BoundingRect" is back to the size it was BEFORE I changed it BUT the buttons are still there!
I don't tend to use many graphics, but with images, after a resize you always need to lock the size & location. Maybe this is the same. Alternatively, you may have set up Geometry Manager to resize the BoundingRect, or you may have a script that does it.

I if now attempt to change the Size of "BoundingRect" the IDE crashes!
Well that shouldn't happen no matter what you do. File a bug report at Bugzilla and attach the stack that makes this happen. If you have any crash logs, they are always useful too.

Wisely I made a backup! I am fast learning the ways of RunRev and it's ability to corrupt or lose stacks and always make a backup before doing anything major.
I've been programming in Rev for years now and the only stacks I lost were one day when I used the "delete file" command on the wrong folder... After learning to cope with HyperCard's ability to corrupt stacks on a regular basis, Rev is very refreshing :-)

Cheers,
Sarah

_______________________________________________
use-revolution mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to