The current method of using the first nine images of the slideshow to populate the slideshow instance attractor grid is efficient (in that it doesn't require manual setup) but can result in a somewhat less than ideal grid of images. For example, in the Weiland grid, the image in cell 7 was scanned with a noticeable white edge, which is a bit visually distracting (it's still a fine image for the slideshow, just arguably not ideal for the attractor grid). There are a few less than ideal images in other slideshows, too.
Since we already know how to set up the grid attractor with manually-specified images, I suggest it would be worth the effort to set up the individual slideshow instances to use manually-specified images. I've lost track of whether we use the same technique for the oral history instance grid attractors as we do with the experience type grid attractors, but whatever approach makes sense is fine (even if that is making copies of the images to store in an attract-images directory as we do with the oral history instances, though it would be nicer to just reference the image item key labels, if feasible).
Below I'll suggest nine images in cell order for the Weiland slideshow that can be used to implement this. After that update is merged, I can either update the other slideshows following the Weiland example or create a ticket specifying the nine images to use in each grid attractor.
The current method of using the first nine images of the slideshow to populate the slideshow instance attractor grid is efficient (in that it doesn't require manual setup) but can result in a somewhat less than ideal grid of images. For example, in the Weiland grid, the image in cell 7 was scanned with a noticeable white edge, which is a bit visually distracting (it's still a fine image for the slideshow, just arguably not ideal for the attractor grid). There are a few less than ideal images in other slideshows, too.
Since we already know how to set up the grid attractor with manually-specified images, I suggest it would be worth the effort to set up the individual slideshow instances to use manually-specified images. I've lost track of whether we use the same technique for the oral history instance grid attractors as we do with the experience type grid attractors, but whatever approach makes sense is fine (even if that is making copies of the images to store in an
attract-imagesdirectory as we do with the oral history instances, though it would be nicer to just reference the image item key labels, if feasible).Below I'll suggest nine images in cell order for the Weiland slideshow that can be used to implement this. After that update is merged, I can either update the other slideshows following the Weiland example or create a ticket specifying the nine images to use in each grid attractor.
Weiland grid images
1 - ric-weiland 2 - development 3 - commencement 4 - diary-3 5 - license-plate 6 - microsoft 7 - personal-notes-2 8 - albuquerque 9 - weiland-gates