>If you use the "built-in" scrollbars for the group, you won't have
>to worry about setting any scrollbar properties. You can set
>horizontal and vertical scrollbars for groups in the group
>properties palette.
Thanks I discovered this after I sent my last plea for help - it
certainly makes life easier!
>Here's a suggestion (it still requires some struggling).
>
>First create a graphic rectangle and set its width and height to the
>likely maximum width and height of the group. These are the overall
>dimensions, not the visible height and width. (You can adjust this
>later after editing.)
>
>Make a group from the rectangle. Set the scrollbar properties.
>
>Set the width and height properties for the group. These will be the
>visible dimensions of the group. Position the group where you want
>it. Set the lockLocation property to true. (If you don't do this,
>the group will resize to its full size (formattedHeight and
>formattedWidth) whenever you edit it. Not pleasant!
>
>When you edit a group, its scrollbars won't be visible while in
>editing mode. So first you need to scroll to the position you want
>to edit, then go into editing mode. When you need to edit in a non
>visible location, you need to come out of editing mode, adjust the
>scroll, and go back in again.
>
>When you've finished the editing, hide the rectangle. This will
>force the group to shrink to the overall dimensions of the objects
>in the group.
>
>Let me know if you find an easier way to do this. :)
>
>In general, I prefer to get all the objects I need into a group
>first, and then set the various sizes and locations afterwards by
>script.
>
>Cheers
>Dave Cragg
I like the idea of the big rectangle to establish the right sized
group. I did something similar (but less elegant) by having a large
text field that I moved down the group to make space as I added more
element to the 'page'. Once I'd arranged all the elements as I
wanted them I threw away the text field.
I couldn't find a better way than your or my method, so unless one of
the real MC experts tells us differently, it looks like this approach
might be the only way.
I was surprised that MC stacks/windows can't have scrollbars and the
vScroll property. I've used this feature in SuperCard, HyperCard and
ToolBook developments. This is why I tried to use a 'sub-window'
approach initially.
Thanks again for the help.
Peter
--------------------------------------------------------
Peter Reid
Reid-IT Limited, Loughborough, Leics., UK
Tel: +44 (0)1509 268843 Fax: +44 (0)1509 264986
E-mail: [EMAIL PROTECTED]
Web: http://www.reidit.co.uk
