Imported Fireworks images don't retain down state image

[tradle]

All -

Apologies if I'm missing fundamentally simple here, but I cannot get a NAV bar to behave as I expect it to. I created a NAV bar in Fireworks MX, and in that environment, everything works great; when a button is clicked, it retains the down state image until a different button is pressed. In DreamWeaver, however, the down image doesn't remain after the click. In other words, as long as the mouse button is depressed, I see the down image. As soon as the requested page loads, the button that had been pressed returns to an up state.

I've tried everything that I know to try. A sample of the code from one of my buttons is below. Any suggestions would be very much appreciated.

 <tr> 
          <td><a href="../FinSvcs.htm" target="_self" onmouseout="MM_nbGroup('out');" onmouseover="MM_nbGroup('over','tfgsNAV_r3_c1','../tfgsNAV_r3_c1_f2.gif','../tfgsNAV_r3_c1_f4.gif',1);" onclick="MM_nbGroup('down','navbar1','tfgsNAV_r3_c1','../tfgsNAV_r3_c1_f3.gif',1);"><a href="../FinSvcs.htm" target="_self" onClick="MM_nbGroup('down','navbar1','tfgsNAV_r3_c1','../tfgsNAV_r3_c1_f3.gif',1)" onMouseOver="MM_nbGroup('over','tfgsNAV_r3_c1','../tfgsNAV_r3_c1_f2.gif','../tfgsNAV_r3_c1_f4.gif','Image1','undefined','../tfgsNAV_r3_c1_f3.gif',1)" onMouseOut="MM_nbGroup('out')"><img src="../tfgsNAV_r3_c1.gif" alt="Financial Services" name="tfgsNAV_r3_c1" width="195" height="83" border="0" id="tfgsNAV_r3_c1" onclick="../tfgsNAV_r3_c1_f3.gif" ondblclick="../tfgsNAV_r3_c1_f3.gif" onmousedown="../tfgsNAV_r3_c1_f3.gif" onmouseup="../tfgsNAV_r3_c1_f3.gif" onkeypress="../tfgsNAV_r3_c1_f3.gif" onkeydown="../tfgsNAV_r3_c1_f3.gif" a.href="../FinSvcs.htm" /></a></td>
          <td><img src="../spacer.gif" alt="" name="undefined_2" width="1" height="83" border="0" id="undefined_2" /></td>
        </tr>

Thanks,
Tim

 

[Microbe]

I think it will only work in frames...some one will be sure to correct me if I am wrong.

Steve Davis
ttf(a)HaHaHa.com.au

http://www.HaHaHa.com.au/weblog

Me? I can't even spell ASP!

NOTE: This sig does not include any reference to voting, stars, or marking posts as helpful as doing so is cause for membership termination.

 

[traingamer]

You need to have different code for the button on the "current page" to show the depressed state.
Did you use all of the code generated by Fireworks or just copy the buttons from one page to the next?

It's kind of hard to tell with the code from just one of your buttons - include the code form two of them and let us know which button should be depressed.

traingamer

 

[tradle]

Traingamer -

I completely see what you're saying about having a different state on the "current" page, and think I'll need to amend my template in order to accomodate the behavior.

To answer another of your questions, I used all of the code generated from Fireworks on the template only. I think I'll change it around and be able to show the down states as I expect.

I'll post again if this suggestion doesn't work; as of right now, the code for all of the buttons look the same.

Thanks,
Tim

 

[traingamer]

Excellent - looks like you're on the right track.
I typically have just the down image for the current page (i.e. no rollovers) like:
<td><img name="navbar_home" src="images/navbar_home_f3.gif"...

while the rest of them look like what you posted.
Hope that helped.

traingamer

 

[tradle]

Traingamer -

Thanks so much for triggering my brain on this. I recreated my template such that the NAV bar was editable. I then edited each page, as you suggested, and made sure that the down state was correctly reflected on each page.

It now makes sense that the states respond correctly to individual behaviors within a page - but do not have the ability to affect the behaviors on another page. I made an assumption about the integration between Fireworks and Dreamweaver that I shouldn't have, in that the NAV bar behaviors could be set for each page with a single set of images and logic. That isn't the case.

Thnaks Again!

Tim