Well, as long as you call DynarchMenu.setup after your elements are generated, it should work fine. Just make sure you assign an ID to those elements that that you pass the correct ID in the class attribute of the LI defining the context menu, as described in the sample files related to context menus. I can provide further assistance if you can show me a piece of code to work on. ;-) A test URL would be great.

You will be able to upgrade for free for 6 months.  The policy is not yet established further than that, but most probably you will have discounted upgrade prices after the 6 months period.

You will be able to update for the price difference, but you will have to contact us before (the process is not yet automatic).

We decided to discontinue it for now.

Yes.

We can't comment on that for now.

Ooops! The popup editor seems no function correctly, the format of my post are missing. Sorry.

Hello.

Yesterday i posted a very ugly formated message to request some improvements. Sorry for the inconvenience. This is again (more or less) the same message with the correct format an a more extended explanation.

Can dynarchmenus be configured 'draggable', 'Scrolabble' and with a more acurate timeout?

• Draggable: Besides of obvious use as menus, I plan to use your dynarchmenus as a tooltips for a help system, with complex HTML inside of the toltips. The tests that I have been able to do with the evaluation menus they are satisfactory, but i also need the tooltips to be draggable. Is this possible?

• Scrollable: In a very large menu that hides in the lower part of the page, can you provide some mechanism to scroll the menus to make them visibles?

• More Timeouts: In the electric menus, they are two timeouts. Can you provide a one more? This is what i need:

- A timeout (500 mseconds or so) for the first level menus, when all the submenus are hidden.
- A timeout (100 mseconds or so) for the navigation between menús, when some submenu are vissible.
- A timeout (1000 mseconds or so) so that the submenus disappear if no option is selected or nothing is clicked.

Maybe all these functionalities already exist in dynarchmenus, but I have not been able to find them in the documentacion of the demosntration version. If they do not exist.. Is possible to implement them? Is eassy? Are they good ideas for dynarcmenus?

I d'ont need these improvements now, but after three or four months. Maybe I myself can code them, but javascript and DOM are not my specialty, I am a PHP coder.

Thanks for your patience. And sorry for my english.

You can have multiple menus. You must initialize them one at a time, the same way you init a single menu; just make sure that the <UL>-s have different ID-s ;-)

As for the "fixed" stuff, there are several solutions:

1. [the most straightforward; doesn't work with IE].  Embed the top level menu in a DIV with style="position: fixed".  Then feel free to position that DIV anywhere you want.  Like this:

   <div style="position: fixed; left: 10px; top: 10px">
     <ul id="menu">
       ... the menu content
     </ul>
   </div>

   "position: fixed" is in the CSS specification for many long years now.  But, IE/Win does not support it.
   

2. Use an IFRAME for the page content.  The menu works pretty well with this in Gecko and Internet Explorer 5.5+, but fails on Opera, Konqueror, Apple Safari (browser bugs; they show the IFRAME on top of the menu).  However, the next version will contain a demo that shows this technique.

3. Use "position: fixed" for all browsers except Internet Explorer.  Work around Internet Explorer bugs by using a technique to emulate fixed position.