Hi Ruth,
We really appreciate your inputs.
Is there any Javascript that we could use in order to suppress this unwanted effect. Further, it only appears when the Milonic javascripts are active even if there is no data in the "data" file - something we also tried.
So for us, it tells us clearly that there is a function in Milonic that slows down something.
If you think a little bit of extra code is necessary as a workaround, we will be terribly happy about giving a big try.
As a side note, we are really surprised that we are the first ones to come across a conflict between the image maps generated by Dreamweaver MX and Milonic's menus.
Many many thanks for your ideas and very best,
John
Conflict between Milonic and Macromedia javascript DMW MX
Hi John,
There have been others who have tried to figure out a way to stop the mouseover/out from working as it does. It's really not a fault in the menu, if you were on a page without the menu but which has images swaps on mouseover they would do the same thing, on mousing on it would change the image and on mousing off it would swap it back. The reason you still see the function even when you have the menu but leave it empty is that you do have an image and you have a menustyle declared and mouseover/out is the default in the menu. I had a couple of ideas, though I don't know you'd want to use either.
1. Changing your image swap function to an onclick event instead of onmouseover and putting a 'heading' in the section telling them to click to get more information on the topic of their choice [or something like that]
2. Getting rid of the onMouseOut [the onMouseOut restore image] part of the code so the image doesn't switch back?
I am not a programmer, nor a javascripter [if that's a word], mostly I'm able to kind of 'see' what the menu is doing in everyday terms. I couldn't write a function for you, but I think that's what you need. I believe it would be a pretty involved function: you'd need a delay written in it, and it' would have to be applied to each of the 5 links, I believe, and then you'd also need if statements I think referring to each item and what has to happen in each instance [mouseon/out] i.e. if item one and mouseover do this, and so on. You might post a new topic with a different subject line and explain the issue and see if you can get help with a function. I'm sorry I can't be of more help. There may be someone else with more knowledge who can help you.
Ruth
There have been others who have tried to figure out a way to stop the mouseover/out from working as it does. It's really not a fault in the menu, if you were on a page without the menu but which has images swaps on mouseover they would do the same thing, on mousing on it would change the image and on mousing off it would swap it back. The reason you still see the function even when you have the menu but leave it empty is that you do have an image and you have a menustyle declared and mouseover/out is the default in the menu. I had a couple of ideas, though I don't know you'd want to use either.
1. Changing your image swap function to an onclick event instead of onmouseover and putting a 'heading' in the section telling them to click to get more information on the topic of their choice [or something like that]
2. Getting rid of the onMouseOut [the onMouseOut restore image] part of the code so the image doesn't switch back?
I am not a programmer, nor a javascripter [if that's a word], mostly I'm able to kind of 'see' what the menu is doing in everyday terms. I couldn't write a function for you, but I think that's what you need. I believe it would be a pretty involved function: you'd need a delay written in it, and it' would have to be applied to each of the 5 links, I believe, and then you'd also need if statements I think referring to each item and what has to happen in each instance [mouseon/out] i.e. if item one and mouseover do this, and so on. You might post a new topic with a different subject line and explain the issue and see if you can get help with a function. I'm sorry I can't be of more help. There may be someone else with more knowledge who can help you.
Ruth
There might be something that could be done in the program, adding or changing something, but I have no idea how difficult it would be since I know any change tends to change a lot of things. If you have a professional license you might contact Milonic and ask for help on this since the forum doesn't seem to have an answer for you.
Ruth
Ruth
But the forum has given an answer... at least in terms of what's causing the problem. Your analysis of the cause was right on the mark Ruth. And your proposed solution was pretty good too; delaying the restore function under a specific circumstance would be the way to go. You should learn more javascript Ruth... you'd be a natural!Ruth wrote:...since the forum doesn't seem to have an answer for you.
JohnH ,
It's actually the MM_swapImgRestore() function in your swapimgrestore.js file that's causing the flicker. The function is called from the onmouseout event, so it briefly restores the default center image as you mouse from one cell in the table to another. The function is, in fact, called every time you mouse out of one of the table cells in your menu. If you mouse out of a cell, and into another, then the MM_swapImgRestore() function is followed immediately by the MM_swapImage() function, changing the center image again... hence the flicker. This cycle occurs whether the menu code is in or not. But with the menu code out, the cycle from one function to the next occurs faster. So the image swapping still occurs, but it hapens so fast that you essentially don't see it (maybe you would on a slower machine... BTW, I see it in NS7 too). So, the menu isn't necessarily interfering with the image swap functions, it's just slowing them down a little; just eough so that you notice the swap. Why the slow down? I don't know for certain without testing, but I imagine two possibilities: (1) perhaps the menu code implements a repetitive timer or iterval function to periodoically check for menu events, (2) more code in the page equals more processing required.
So... what to do about it? The problem is essentially in how the image swap functions work. They're generic, and usually pretty good. But in this specific situation, they aren't good enough. If it were me, I'd write a different set of swapping functions that are designed specifically for this situation. They would be fairly straight forward (actually less complex than the MM_ functions you now use), and would be designed specifically to prevent the flicker. If you need some help with that, I could probably lend you a hand early next week (won't be on the forum any more this weekend).
Cheers,
Kevin