Problem with Menu overlaying MenuTree (submenu).

Poster: Boris
Dated: Thursday January 25 2007 - 16:14:49 GMT

Well, I've run into a few more problems that I'm curious if anyone has seen before or if somebody can help me with. I've tried a few JS tricks, but they don't seem to work. I've tried changing Z-order of various menus which didn't work either.

Here's an animation of the problem, which I'll explain below:



Frames:
1. Menutree and menu are on the same page (initial state)
2. Hover over Tab 1 in the menu and it overlays the root nodes of the menutree just fine
3. Open up one of the nodes
4. Hover over the menu again and notice that the root node in the menutree "Tab 1" does not show up, however the text "Menu 1.x" all show up *BUG*
5. Hover over to a menu right next to the one we just highlighted and notice that the bug is fixed
6. Hover back to the menu that had the bug and again it's fixed

Conclusion: it seems like the menu does have the code to internally change the Z-order or do whatever it does, but that code seems to be executed in the wrong place in the code (or maybe it's the right place, but a similar call should be made in another place as well).

Not having an easily readable mmenudom.js file, I don't want to mess with the JS within that file, so hopefully somebody here can help me either create a work-around or fix this bug. Since the menu [probably] wasn't originally designed to also be used as a tree control, I understand why a "submenu" would show up, while the main menu would be hidden. I just wish the same style could be applied to the sub-menu's.

I hope my explanation made sense. Please let me know if you need any other information from me to help solve this problem.

Thank you,

Boris

P.S. Off topic: Does this site allow local hosting? Our firewall blocks any image hosting sites and in case this information will be archived, I will not keep the images forever on my personal site.

Poster: Boris
Dated: Thursday January 25 2007 - 22:11:56 GMT

The other issue we have with the menutree is that the expand/collapse images navigate to the URL of the menu.



In a tree control, the navigation images which expand/collapse the node should NOT navigate to the URL of the node unless the node/container is pressed.

Is there a way to make this control act more like a tree control in windows?

Thanks again,

Boris

Poster: Ruth
Dated: Saturday January 27 2007 - 1:19:43 GMT

Hi,

You are going to have to put up a test page for us to provide help on these issues. I really have to see the pages and experiment.

Ruth

Poster: Boris
Dated: Monday January 29 2007 - 22:22:24 GMT



Ruth,

Our corporate policy won't allow me to put up our internal sites, however I wanted to create an example for you based on this menu: http://www.milonic.com/treemenu/tree/. Unfortunately as soon as I try to use the latest treemenu.js file with that example (I modify nothing besides replacing the file with 1.26) I get errors in IE, and functionality doesn't work at all in FireFox.

I'll have to create something from scratch and post the code here later on.

I also wanted to add that the two functions: openBranchByName and closeBranchByName should probably be modified to accept another identifier. For example, I modified the code to read as follows:



Notice that it takes in a parent name. Because a menu name can be the same in two submenus it's good to be able to differentiate between the menu's. Or maybe it'd be better to add functions to openBranchByItemNum or whatever. Default behavior would pass in a null, so only a top level menu would get opened.

Andy, or someone: In any case, I hope the example menu that you have on the site can be fixed to work with the latest JS. In the mean time I'll try and create a basic example that I can share with the latest JS files.

Thanks again,

Boris

Poster: Ruth
Dated: Tuesday January 30 2007 - 6:39:27 GMT

Hi,

All I really need is a page that has the two menus in the same position so I can see the problem and work on it.

I'll post to Andy for the other, though I believe that particular treemenu is still being developed. I know the collapsible one works, but I haven't used the tree, though the one on the site does not give me errors in IE or FF.

As to the openbranch and code modification, that again Andy will have to address. I have no knowledge of js code or programming.

Ruth

Poster: Boris
Dated: Tuesday January 30 2007 - 19:05:38 GMT



Ruth,

Thanks a lot for the offer to help! While making a sample for you I actually figured out one of the problems. I had to change the zindex of every sub menu in the primary menu (that overlays another menu) to 1010. Setting them to 1000 or 1001 (999 being default) didn't do the trick. It seems some menu's for some reason get Z-index of 1000 or 1001.

Here's an example directly from milonic.com site:


By the way, the issue I described in the second post still exists. I copied the menu available on this site (only put the latest JS files in) and made it so the "Desktop" node is both a link and a container (has URL set).

To explain what I mean, do the following:
1. Navigate to this page
2. Click on the "Edit Pencil User Manual" node
3. Click on the "Desktop" node
Result: you got a popup that you're navigating away from the site.

Now, follow step 1 and two, but this time instead of pressing "Desktop" in step 3, press the [+] to the left of Desktop. Technically this should open up the node, not be a link along with the rest of the item.

I hope I'm explaining myself well enough. Let me know if what I wrote doesn't make sense.

Thank you very much!

Boris

Poster: Ruth
Dated: Tuesday January 30 2007 - 19:40:04 GMT

Hi,

Yes, I understand what you're saying on the click image or click text. As I said I am not a programmer so that would have to be something from that end.

I would never have thought to have that but then when I go to a site with a menu I have never thought to click the image by itself

As to the other issue on the z-index, since you found a fix that's great. I wouldn't be able to comment without seeing the page and figuring out though experiments why it was happening. I know some people do things with z-index, but I've only seen a couple of posts about it. In most circumstances, I think the built in z-index works for what most do.

I'm glad you resolved the issue. As to the treemenu you're using you might contact Milonic direct about that issue. John, Kevin and I are only volunteers on the forum and don't work for Milonic. We just really, really like this menu

Ruth

Poster: Boris
Dated: Tuesday January 30 2007 - 20:38:02 GMT



I've read plenty of your posts.. you're too humble




Yes, I've read that. I'm really glad you guys help people out. I hope you guys get free licenses whenever you want for all the effort you put in!

About contacting Milonic directly, I wasn't sure that I could without being a customer--waiting for everything to get approved and paid .

About the tree navigation, if you use Windows, open up your Windows Explorer and click on a folder on the left pane. Notice that the contents of the folder now show up in the right pane. Next, click on a [+] or [-] for another folder. Notice that the right pane didn't change. This is typical behavior for a tree control.

Boris

Poster: Ruth
Dated: Tuesday January 30 2007 - 21:20:10 GMT

I think that my brain separates things, so I never put together how the tree in windows worked with the webpage menus using a tree structure.

I think you may be right on the contact issue since they get so many support requests from professional license users.

Ruth

Poster: Andy
Dated: Thursday February 1 2007 - 11:42:34 GMT



Not at all - we will do what we can but can't gaurantee anything.

Anyway, I beleive this bug to have been fixed in the latest release

Let me know if not

You may only need to update http://www.milonic.com/treemenu.js to get it to work

Cheers,
Andy

Poster: Boris
Dated: Monday February 5 2007 - 19:50:54 GMT



Hello Andy,

Thanks for the info, and seems we already purchased the product.

I'm not sure which fix you've implemented, but I got that latest JS file it didn't change the way the tree looked or worked, however doing a compare on the file I finally figure out another bug that I was having--for which I may post a thread if our customers find it .

Thank you,

Boris

P.S. The real problem is the way the tree functions as described in my post #2.