Field output rewrite uses info from previous slide when using ThumbnailHover

you can use Global: Custom text field to achieve the desired result.
maybe its not the best solution, but i guess it can solve your problem.

It looks like there is definately an off by one error someplace. I just discovered the same/similar issue: rewriting a field (to combine items) would end up with some info from the current result row, but some from the previous result row.

Changing from Slideshow to HTML List, the combined rewritten fields are correct (AA BB CC), then switching back to Slideshow, I end up with A (The Main Item) and thumbnails with AB BC CD DE EA (or something like that... you get the idea)

I'll see if I can track it down now... this is a pretty major bug and I need this functionality.

Ok, narrowed the problem down to how it occurs:

If you set up your rewrite to use the _current_ field, something gets confused, and will start using the previous field(s)... I believe (after some quick glance at the code in views_slideshow_thumbnailhover.theme.inc that due to the field(s) in question being displayed or not, combined with trying to change the existing field into a rewritten field (ie change field B3 to become B1-B2-B3) and it's falling back to the previous field values (ie B3 becomes A1-A2-B3 or B1-B2-A3, not sure which is the case here, still debugging under a time crunch to just get it working) which aren't being reset to empty inside the loop.

This is why using a fresh "custom text" field fixes the problem: it's not part of the field mix that it ends up becoming so it's exempt from the confusion and misloading of older values.

Yes, it's still got an off by one error someplace.

If you dump the view->result (or rows) the order is as expected, but somehow the items rendered in the breakout are incorrectly, with the last item _first_, throwing the entire breakout off by one.

And this is a code error, not an user interface error, so please don't change that.
The display is wrong, but it's clearly someplace in the code that needs to be fixed, not a interface problem.

The off by one error is solvable by following directions here:
http://drupal.org/node/774056#comment-2917816

"Exclude the fields that are in your custom text
and you will need to check the boxes to include those fields in the slideshow."

If you don't check to include the fields in the slideshow, the theming function grabs incorrect info, leading to the 'off by one' error. I narrowed the problem down to

$view->field[$field]->theme($node);

Which pulls the wrong info as a result, despite being given the correct node.
(passing it the first node, it ends up returning the _last_ node's rendering instead).
Checking all of the fields used in the custom text eliminated this, returning the correct field/node rendering.

Hopefully the patch mentioned there in #774056: Thumbnail Hover - main frame ignores views tpl override as 'in a future release' will truly solve this. Not marking as duplicate, as that issue is already closed (and a support request).

Can you see if this patch renders items better?

Friends don't let friends write patches when tired. This should be a better patch, but I'm glad it's working.

Yes, that patch works, and removes the (incorrect IMHO) requirements that items be included on the slideshow itself even if not displayed. It introduces a bit of a confusing conflict of options in that you can mark a field as "Exclude from display" and if checked in the slideshow settings, it will appear anyway... But this is still better than the unpatched version.

+1

Thanks for testing. Yeah this makes marking exclude from display not really necessary anymore, but maybe in the future I can make it so that if an item is marked excluded from display it isn't an available checkbox in the slideshow settings.

Actually was easier than I thought. Can you please review this one which removes the field from the slideshow settings if it's set to be excluded.

oops, changed version incorrectly. Patch is for 2.x-dev...

Oops... found a bug in patch-3
given field A, set it for visible.
Set slideshow to display it (checkbox).
Now set field A as not visible for display.
Checkbox for slideshow vanishes, but field is still used (and visible)

You should display all checkboxes, but maybe make them disabled (uncheckable), and ensure the value is forced to not usable?

This is going to be tough. To make it not display you would have to resave your settings. I can see about checking if the field is excluded before displaying.

Don't listen to me when I say it's tough. I just cut out more than I should have.

Patch committed.