Installed build from 09-Apr. Slideshow now working but some questions, understanding it's in progress:

* I expected the sized image, not a small thumbnail (it's not even that as some are larger than my setting). What image is being called and will there be a way to control?
* Image change is very fast, can this become a setting (And I'm the one on slow dialup)?
* I have the image description, which I really am glad of but, as above, it goes by fast and type is quite small. Are there/will there be CSS declarations to set (I just love playing with the CSS <GRIN>

1. I can't reproduce this, the slideshow uses the sized image, but you have the option to set a custom size.
The slideshow works this way: If called form the album.php page it starts with the first image, if called from the image.php it starts with that image. Since all images in the album have to be loaded it can happen that the first ones are skipped because not ready, especially if they have not been cached already. If youn don't want that, you can use the flowplayer flash version. (you set that on the themes slideshow.php with printSlideshow()). Please see our functions guide for more info about that.

2. This is a setting see 1...:-)

3. The type is relative size and uses your browser's setting. If you set the size there very small, this will be very small, too.
But you can change the slideshow css. For some reason this is not a css file but printed by a function in the plugin's slideshow.php (the sizes of the slideshow div needs to be dynamically altered if you set another size than the sized image).

Theme options: Should "image size" be set for the size I want to see in the slideshow? I have it matching the crop thumbnail width as I had no idea what it referred to. The sized image I see for the album is okay.

Should I pre-cache images to see if this produces the larger sized image in slideshow?

It would be great if the css file could contain layout formatting.

My flash player option, for no particular reason is set to flowplayer v1.0.0

1. "image size" within the Options was always the size for sized images....that indeed explains why you saw thumbs.

I was wrong above you can not set the size in `printSlideshow()` on the theme's slideshow.php (I am getting confused by my own code....:-)), but in the `printSlideshowLink()` in your image.php or album.php.:
`printSlideShowLink($linktext='', $size='')`

If you don't set a size, "image size" from the options is taken, if you do it will be overriden.

2. The pre-caching has nothing to do with the size.

3. As I said there is no pure CSS file (I need to change the width regarding the size setting so I need it within a function). Take a look at plugins/slideshow.php and the function `printSlideShowCSS($size)`.

4. Flowplayer is the standard flash player and the flash option of the slideshow does only work with it.

version 1.1.5 [1445]

Okay, updated to last night's build: Gave time for the cache to kick in and I do see the sized image. So, I'm assuming it is reading the info from the tab 'theme options'. You say the two aren't related so no idea how it's now working

Would like now to know about speed. It goes REALLY fast and not obvious to click the image for controls which don't always show up (?? slow).

(And, it would be great to adjust layout with CSS......)

[i]So, I'm assuming it is reading the info from the tab 'theme options'. You say the two aren't related so no idea how it's now working [/i]
I didn't say they are not related (ok, I said "gallery options" instead of "theme option", I admit...:-)). The image size of the options is taken for the slideshow image if you don't set a specific one in `printSlideshowLink()` http://www.zenphoto.org/documentation/zenphoto/_plugins---slideshow.php.html

[i]Would like now to know about speed. It goes REALLY fast and not obvious to click the image for controls which don't always show up (?? slow).[/i]
Again, you can set that on the slideshop.php theme page. See http://www.zenphoto.org/documentation/zenphoto/_plugins---slideshow.php.html for the details.

[i](And, it would be great to adjust layout with CSS......)[/i]
I repeat my above answer: Take a look at plugins/slideshow.php and the function `printSlideShowCSS($size)`.

I've looked at the Docs but didn't really understand them. My concern is for every PHP file I modify, updating nightly builds means doing file comparison or otherwise I overwrite. Was hoping this woud be considered for GUI interface (there is a tab already for plugins but it's empty). If this is the case, great.

When I say layout, I mean make the page look part of the album instead of black & white, and teeny tiny font size that I can't read. As in using CSS to control layout.

Will have to put off trying to comprehend the docs until my head clears more (not implying anything, it's valid medical problem I can't get rid of).

It's in your hands not to you overwrite your own custom modified theme. Only the standard themes are updated. Some things are just easier to set within the file. Since you need that option once, it's not that hard to enter a function....

[i]When I say layout, I mean make the page look part of the album instead of black & white, and teeny tiny font size that I can't read. As in using CSS to control layout.[/i]
Sorry, I don't understand where the problem is? Then modifiy the slideshow.php to look like an album page:
- duplicate you album.php,
- delete all the usual album display stuff so that you get the "core page"
- add the parts from the theme's slideshow.php into it, that would be just: `<?php printSlideShowCSS($_POST['size']); ?>` in the head and `<?php printSlideShow(); ?>` in the body.
- delete the original slideshow.php
- rename the duplicated album.php file to slideshow.php

Voila, you have a slideshow.php that looks like an album page...
We really can't do all the work for you. If you want to design something differently, you would have to do some things yourself...:-)

I am using the standard DEFAULT Theme. Hence it's updated. The modifications I've made is the CSS files only, not a "big deal" as anything you add can be caught based on the fact the new item won't match my layout or doing file differences check.

My Gallery opening page to a modified DEFAULT Theme with modified PHP files. I don't worry if they don't get updated nightly as I am only using the first page.

I follow your reply, my head just needs to settle down enough to implement. And, my monitor needs to be still instead of flying around (LOL! That's what vertigo can do). When I say I'm trying to avoid customizing PHP pages it's to make sure they'ree updated when I do a nightly build update. Caught myself with wrong version number to build because I updated the root files but not the zp-core files thinking I first had to modify.

in slideshow.php (DEFAULT THEME)
<div id="slideshowpage">
<?php printSlideShow(); ?>
</div>

If I added (to the slideshow.php file, in the appropriate place)
` <link rel="stylesheet" href="<?php echo $zenCSS ?>" type="text/css" />` (taken from the image.php file)

Would that call the stylesheet and therefore allow me to format the #slideshowpage <div> tag?

`Slideshow.php` has an inline stype sheet, so first, you will have to replace the line `<?php printSlideShowCSS($_POST['size']); ?>` with your link. Second, you will have to initialize the varialbe `$zenCSS` somewhere. This is done in `default` with the call `$themeResult = getTheme($zenCSS, $themeColor, 'light');` This retrieves the CSS set by the theme option.

So, you would need to replace
`<?php printSlideShowCSS($_POST['size']); ?>`
with
`<?php $themeResult = getTheme($zenCSS, $themeColor, 'light'); ?>

<link rel="stylesheet" href="<?php echo $zenCSS ?>" type="text/css" />`

Of course, your CSS must supply all the same items that the inline one did.

Ah, I was not looking at the "correct" slideshow.php". Kept viewing the one in the upload instead of the actual one that is in use, thereby showing the CSS inline Found the styles and will work on adapting for external file, which I prefer.

I did see one declaration empty
` #slides {

width: px;

}`

What value is suppose to be here and should it have been picked up from somewhere in the Admin entries?

You need to make sure that the path to the image for the controls is correct and that the theme file slideshow.php includes the javascripts of the `printSlideShowCSS()`function.

The reason why I didn't made an external css file was that the slideshow was meant to work as a generic one for all themes without adjusting (yes, I was too lazy for that..). At first I neede to change a value of the css by php, which recent changed have made pointless. So I am turing the css into a separate file to reside in the plugins/slideshow folder.

If you wait a little, you can grab the nightly and work from there.

I moved all the inline CSS to the Default Theme's CSS file. But didn't get it working properly, somewhere it's not being called. Was expecting the broken link for controls -- that's okay for my test as I'm using an album with 1 image so it stays still <SMILE>

I'll wait for the build. If it's going to the plugin folder, does that mean I'll have to style it generically for all my albums as each one uses their own CSS? So, if Album1 is blue, and Album2 red (background), would I need to find a common background for the slideshow?

You can't move just all slideshow css into the default css. The body part for example would be double. You have to work a little yourself if you want to change that...:-)

In the nightly each theme will have it's own slideshow.css and slideshow-controls.png image plus as before the slideshow.php page. Of course these are the same for all themes.

Regarding different album designs, that is up to your abilities to manage that..:-)

getFirstImageURL, getLastImageURL
separate slideshow.css files (place in theme folders)

Found in the nightly build trac.... thank you <SMILE> Won't get to play until tomorrow night Will come up with a "neutral" design for the common CSS that each album will use (they're all in the same Default Theme, just different CSS files distinguish them.)