Works here, ex (once again using vac as the load area):
Code:
useButtons : {vac: {0 : true, 1: true, 4 : true, 5 : true}},
But it sounds like you may just want to set that to:
and prior to that set:
Code:
writeControlButtons : false, //Also requires element with id of load_area_idControl ex: <span id="loadareaControl"></span>
This will enable you to create your own buttons/controls. You may use whichever ones you want, and use images, links or buttons, or a mixture. The buttons may be in any order you like. You must have a control element, ex (once again using vac as the load area):
HTML Code:
<div id="vacControl">
<input title="Previous" value="<<" class="vac" type="button">
<input title="Next" value=">>" class="vac" type="button">
<input title="Run" value="Running" class="vac" type="button">
<input title="Stop" value="Stop" class="vac" type="button">
</div>
The value attributes of the buttons/controls can be whatever you like (if using links or images, the value attribute is meaningless), but the title attribute tells the script what the control does and must be one of:
- 'Next' - brings up the next image
- 'Previous' - brings up the previous image
- 'First' - brings up the first image
- 'Last' - brings up the last image
- 'Run' - starts the slide show
- 'Stop' - stops the slide show
AND each control must have the class of the id of the load area (in this case 'vac' again). Whatever the active control is will also be assigned the added class of loadareaActive (vacActive here) by the script, which may or may not be used in your stylesheet to distinguish the active control in some manner visually.
Added Later: This is important, you may also want to set:
Code:
swapControlVals : false,
to prevent the script from overwriting your values (or creating values) for your custom Run and Stop buttons/controls. In some cases, letting the script do this is fine, in other cases it may cause an error and/or a visually undesirable result.
Bookmarks