Glad it worked.. a few final notes.. this method I showed opens up a nice little trick to reduce the files size of images involved in the rollover, as well as reduce the amount of HTTP headers flying around between browser and server. This technique is known as 'CSS sprites'. Just google that term... there are plenty of articles on it..
but in a nutshell:
You could use one image that has both off and on rollover states into one graphic.. so say you had a button that was 30px height X 100px wide... you can create a single image that has both button states stacked (so the image would be 60px height X 100px wide.. and in the intial CSS rule you could instruct the background setup as such:
a.test {float: left; width: XXpx; height: XXpx; background: url(/path_to_image/image_off.gif) no-repeat 0 0;}
then for the rollover state:
a.test:hover {background: url(/path_to_image/image_on.gif) no-repeat 0 50%;}
So when the rollover kicks in, the background shifts vertically by 50%. In doing so, the total file size of the rollover image is smaller than the combined total of two separate images, and the request / response headers are reduced by one. The more related images you combine in a CSS Sprite sheet and use CSS for background shifting and isolation, the more memory and header chit-chat you save.. this effect can really help speed up site downloads and response times. Its a win win situation. You save bandwidth.. users get snappier sites (from an image handling standpoint). Just don't go too overboard in combining and using too many CSS background images.. as I believe this starts to become a burden on browser rendering performance.
Also, don't forget to flag this thread as 'resolved' in the tool threads dropdown menu 🙂
Cheers,
NRG