ambassador at fourthworld.com
Sun Feb 20 16:36:50 CST 2005
>>The other option is to write a REALLY complex resizing script that can do
>>all the math for figuring out the aspect ratio of all objects, and then
>>resizing them according to your stack's width and height, and their own
>>location. If you can handle that then great, but it's one project I won't
> I did something pretty similar : actually I did not resize
> a stack; there was a "grid" of thumbnails of a certain size
> (about 200 by 100 pixels each, don't remember the exact
> figures) arranged in about 80 rows of 5 cols. of course
> all thumbnails weren't visible altogether on a 1024 x 768
> pixels stack, and there was a vertical scrollbar on the right to
> scroll the group of thumbnails.
> But under certain conditions, end users needed to see the
> whole group of thumbnails, and in 1 click it was possible
> to resize the thumbs and rearrange them in a grid of 20 x 20.
> Some thumbs contained imported images, and others were
> empty (according to previous actions of the user). Some
> were also selected (different bordercolor) and others weren't.
> There were actually 2 grps of objects : 400 images and 400
> graphics used for "empty" images.
> Scrolling both grps together, as well as toggling back and forth
> from 5 * 80 to 20 * 20 were quite easy to do using grps and did
> execute very fast...
> So I don't see why such a project should remain out of reach...
Agreed. While it's tedious it's not atom-splittingly difficult.
The basic method is pretty much how you'd implement it in just about any
other language. _Very few_ authoring/programming tools have that sort
of zoom in/zoom out built-in.
Fourth World Media Corporation
Rev tools and more: http://www.fourthworld.com/rev
More information about the use-livecode