Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
725
UltraWebMenu or WebDatamenu: working with MVC?
posted

Hello,

I have seen the forum question regarding controls for MVC.

I 'm not sure now if I can use some of the already existing controls within MVC , like webdatamenu and/or ultrawebmenu.

I have made the following test in MVC:
I have created a three column layout within master page and at the top a navigation area (content placeholder) to be used later on for webmenu with four items. The user should be able to call pages (views) from there.

In the info view (inheritated from master page), I have added the content control and added there the IG ultrawebmenu control with the four items.

I have noticed now that the four items are visible (even with background image) but I cannot navigate that means the hover and active and selected state is not rendered. In other words, you should normally see another colour if you hover over the item and finally navigate to the target URL as given in that item. This does not work.

The Infragistics.Web.Mvc assembly and corresponding script manager is added onto the master page. The EnableViewState is set to false, enhanced rendering is set to TRUE, compact rendering to FALSE.

Is something missing?

Yours
Stephan

Parents
  • 725
    posted

    I have to correct myself:

    ultrawebmenu will work if I have only one IG control on the webpage.

    The complete stuff does not work in the following situation:

     I stilll use a master page with index page inheritated from that master page.
    Now I have created a MVC control like "GeneralNavControl.aspcx" which contains the webmenu control with four items, I also put in there the IG MVC sript manager. The GeneralNav.aspcx will be called within index page with HTML.RenderPartial("GeneralNavControl").

    This will work as long as no further additional IG controls will be added onto the index page. Because these added IG controls again require the IG MVC script manager , you get a Jscript error if you add a second IG MVS script manager in the page index.aspx (= index view). I believe the situation of having several MVC script managers is not valid.

    My question is: how can a manage the situation of having more than one IG control and the IG MVC script managers if the pages are built with master page approach and maybe with additional RenderPartial pages so the IG controls are spread over different pages which will be finally rendered into one page?

    Yours
    Stephan

Reply Children
No Data