nuther new newbie nuisance

[Nonsanity]

Well, it takes code to flip images with buttons, and the scrolling field
needs none. But if you want to write some code anyway, you can also script
the field to randomize the order of the images.

As for cutting them off, that is true... You will get partial images at the
top and bottom while scrolling, particularly if the images are very large.
If they are small, instead of separating the images with returns, one could
use spaces and let the engine wrap as many into view as possible.

If a slideshow-style presentation on each card is preferred, then fields are
not the way to go. But Tim was giving examples of scrolling, so I went with
that. :)

 ~ Chris Innanen
 ~ Nonsanity


On Wed, Jun 15, 2011 at 1:00 PM, Slava Paperno <slava at lexiconbridge.com>wrote:

> This is a brilliant idea (using a character as a placeholder for an image),
> but what's the advantage of having a bunch of images in a scrollable field
> vs. a series of images with the Next and Previous (and maybe Any)  buttons?
> And maybe an option for placing up to four reduced images on the card at
> the
> same time, for comparison? Scrolling is a pain to begin with. The order of
> images in the scrolling presentation will always be the same. There will
> always be partial images on the screen as you scroll--just the head or just
> the legs. If you have a series of images, each stored in its own location,
> you can call them up in any order, including random order, and arrange them
> any way you like.
>
> S.
>
>