hi on my horizontal menu that drops down to vertical for submenus, it seems that in the active state with no mouse over the menu looks fine, but when i hoover over a horixontal menu item its effect is that of being 'de-pressed'. ithink that this effect is accomplished thru a simple cell padding left= 1px, top=1px. how do i get rid of this?

hi on my horizontal menu that drops down to vertical for submenus, it seems that in the active state with no mouse over the menu looks fine, but when i hoover over a horixontal menu item its effect is that of being 'de-pressed'. ithink that this effect is accomplished thru a simple cell padding left= 1px, top=1px. how do i get rid of this?

I've been playing around trying to get context menus working on images, with a different menu for each part of the image and with the ability to process information about the part of the image the menu was activated from (it's for drill down grpahing in case anyone is wondering). Anyway, I've pretty much got it working the way I want but ran into an issue with Opera that stumped me for a bit and I thought I would report it.

My test script is located here... http://mrchook.homeip.net:1500/~mca/test/context_menu/img_context.htm

To do what I wanted I used custom parameters on the AREA tags in the image map to hold the arguments relating to the area and custom parameters on the LI tag that forms the menus to determine the menu action and then used a custom javascript handler to process the action like this...

  function my_handler(action) {
      var item = action.info;
      var triggerElement = item.menu.target;
      var arg1 = triggerElement.getAttribute("arg1");
      var arg2 = triggerElement.getAttribute("arg2");
      alert("menu_action = " + action.params.getAttribute("menu_action") + "\narg1 = " + arg1 + "\narg2 = " + arg2);
    };

This works very well.  Now to the problem, if I replace the custom attribute name with "action" (which I originally used, hence this problem) instead of "menu_action" then Opera 8 thinks that the action is, for example "http://mrchook.homeip.net:1500/~mca/test/context_menu/action_1" instead of just "action_1".  It works fine in FF and IE with either name.

The only other problem I can see is that the context menu should work for both left and right click, however for IE it only works on the left click.  I can't seem to see where I have gone wrong on that (also, Opera only works on the right click but that's another issue I already know about)

Cheers,

Michael

Hi Mihai,

I downloaded the eval version yesterday night and I have to say it; I'm amazed on how straight forward it was to come up with simple menus. Very cool stuff you have put together.

I just finished read all threads and I have a few questions:

1) How do you do the nifty floating menu you have on the left hand side of your site -- I presume it is easy to do with the DynarchMenu, but I did not find an example and the pages on your site are a bit of a challenge to reverse engineer for my limited JS understanding. So a minimalist example like you have for the other features would be cool.

2) How do you get the context menu to show up at a mouse click? See right-click functionality is something very few people would expect on the web... cuz it has been so hard to do till the DynarchMenu came about ;-). Anyway, the idea to use the context menu is to simply put an anchor tag that says "options" and when the person clicks on it the context menu shows up.

3) That also means that there would be about 100-200 span/div tags where the context menu(s) could be called from. Would my page be slow to initialize with that many items?

4) On the context menu, is there a way to set up a callback function before activation so that we can disable/gray out menu elements that are not applicable to that instance of the div/span?

5) Please don't shoot me, but I have to ask... will DynarchMenu work on WebTV "browsers" ?
* ducks... * ;-)

Thanks.

Your menu and your calendar rock!

Want to eliminate the small image area at the left of the text of a menu item. I have not found out where this is defined. Really just want the text flush to the left of the menu maybe with a small 1 or 2 pixel margin. The area defined for images is too large.

Thanks

Not sure if this is why, but after installing the registrered version some of our menus do not work in NS or FF but do in IE....IE on the PC but not on the Mac. Still trying to track things down but how could a menu just not show at all on one browser and work fine on another?

This relates a little to my earlier post regarding namespace poisoning in Opera (only in that it's the same code). The example is now at http://tams.com.au/~mca/image_context_menus/img_context.htm .

The problem I'm having is getting a consistent interface across the 3 browsers that I care about (Opera, Firefox and IE). I have set it to activate on both left and right mouse buttons which works fine in FF but I can only get right click in Opera and left click in IE. I'd be happy to have only one button to activate the menu but I'd like it to be consistent if at all possible.

Is it possible to capture the right click event on an img tag in IE ? That seems to be the problem (i.e. I'm seeing the normal context menu that you see when clicking on an image)

Cheers,
Michael

Hi Mihai,

...I made quite a bit of progress from yesterday ;-)

A couple of more questions:

1) Is there a limit as to how many times we can attach a menu to an object with something like this (perhaps a memory leak, a browser bug, or something like that)?  I would like to create some 10 individual context menus and attach then to different objects as the selections in a form change, so there would be  no limit as to how many times they would be reassigned.

var e = document.getElementById('my_element_id');
e.className = 'my_class dynarch-menu-ctxbutton-left';
DynarchMenu.setupContext(e, my_global_context_menu.items['my_sub_menu_name']);

2) Is there a way to have the context menu positioned in relation to the <span>, <img> or <a> tag we are associating it with?  I wanted to make it aligned as if it were a drop down menu and the <span>, <img> or <a> were its "parent".   So it would drop down left-bottom-aligned to that control/tag and not pop up next to the mouse pointer as the samples do.  It would make for a more "organized" look.

BTW: The lazy initialization rocks!  The attaching of the menu to 200 tags I asked you before was fast and worked like a charm.  The setupContext function above solved most of my problems, it would be nice to be able to disable/gray out individual items as we talked about before, but for now I could display "you-stupid-user type messages ;-)".  Overall I'm really impressed. So far I have been able to figure out how to do everything I want to with your menus. :-)

One wishy-washy, but nice to have feature... a standard ready-to-plug-in "preferences" menu with the ability for the user to save the settings in their cookies.

:-)