-
You can access the property on the client-side like this, var canRaiseSave = MenuItem.getProperty("CanRaiseSave"); And you can set it like this, MenuItem.setProperty("CanRaiseSave", true);
-
Yes, the page life cycle executes as usual, in case the CallBack's response depends on other controls or something in code-behind. Only render is aborted and replaced with CallBack's response.
-
On client-side you can select the parent node by, NavBar1.selectItemById(NavBarItem.get_parentItem().get_id()); I don't understand what you mean by "change the body" can you explain it?
-
Do you have Smart Navigation enabled in your website? Try setting it to false.
-
Yes, dialogs can be placed anywhere in the page, and can be called from NavBar. You can also try setting EnableViewState="false" to see if that speeds up anything. Also make sure you are running the application in debug mode.
-
It is probably due to a layout issue, can you explain the layout or possibly post the container code and CSS. Forum is mainly for peer-to-peer support as noted in the post/reply page. For guranteed and timely response please use our online support form Someone will get back to you, and you can attach the related code to speed up the process.
-
Can you post the server-side Callback handler code? Usually it is a good idea to test the server code without the callback to make sure its error free. You can also set Debug="true" in the callback control to see the actual error.
-
In your xml file have the tab id and product id And function could be something like this, ClientSideOnTabMouseOver="TabStrip1_OnTabMouseOver" function TabStrip1_OnTabMouseOver(tab) { ajax_showTooltipr(tab.ID, tab.GetProperty("ProductID")); }
-
It should be something like this, ClientSideOnTabMouseOver="TabStrip1_OnTabMouseOver" function TabStrip1_OnTabMouseOver(tab) { //your logic here }
-
Yes, you can hook up the NodeSelected event and call Menu1.show() method to do this.