User Profile & Activity

Glenn Layaar Support
Page
of 99
Posted: July 25, 2010 11:10 PM

Based on my test, the issue seems to be caused by update function. This function will trigger an asynchronous call, so we will not br able to add another row while the grid is still processing.

Here is a workaround so multiple row could be added during client side event handler:

function AddGridRow()
{
var grid = ISGetObject("wgTest");

var maxRow = 2;
var i = 0;

var updateProcess = setInterval(function ()
{
if (!grid.IsInProgress && i < maxRow)
{
var newRow = grid.RootTable.NewRow();
var cells = newRow.GetCells();

//Add cell logic

newRow.Update();

i++;
}

if (i >= maxRow)
{
clearInterval(updateProcess);
updateProcess = null;
}
}, 15);
}


Since you are already using WebFlyPostBack, my suggestion is to use WebFlyPostback for all the scenario. There might be incompatibility if we mix the use of UpdatePanel and during FlyPostBack.

I have update your attached sample to completely use WebFlyPostBack. The upButtons section is changed to a panel for simpler update.

Unfortunately, I could not find any documentation for the FunctionParameter, but I believe it also accept numeric data type and boolean.

UPDATE: this thread is still an ongoing discussion

The attached sample already use both WebMenu and WebGrid. Both issue could be solved using WebFlyPostBackManager as demonstrated in the attached sample on my previous post. No javascript error encountered in the sample.

Posted: July 22, 2010 10:27 PM

Based on my analysis of the code, the submenu snippet is:

<Intersoft:UXStackButton Text="Test" Icon="/JTS2;component/Assets/Images/Home.png" NavigateUri="/Views/Home.xaml"/>
<Intersoft:UXStackButton Text="Company" Icon="/JTS2;component/Assets/Images/my_contacts.png" NavigateUri="/Views/CompanyView.xaml" />
<Intersoft:UXStackButton Text="Designations" Icon="/JTS2;component/Assets/Images/notepad.png" NavigateUri="/Views/DesignationView.xaml" />
Since in the URI mapper you already define this rule
<Intersoft:UriMapping Uri="/{page}" MappedUri="/Views/{page}.xaml"/></Intersoft:UriMapper>

The correct navigate uri property for the submenu will be:

<Intersoft:UXStackButton Text="Test" Icon="/JTS2;component/Assets/Images/Home.png" NavigateUri="/Home" />
<Intersoft:UXStackButton Text="Company" Icon="/JTS2;component/Assets/Images/my_contacts.png" NavigateUri="/CompanyView" />
<Intersoft:UXStackButton Text="Designations" Icon="/JTS2;component/Assets/Images/notepad.png" NavigateUri="/DesignationView" />


Posted: July 22, 2010 4:11 AM

My test show that using UXStackItem instead of UXNavigationButton will solve the issue. The UXStackItem has already support navigation so it would behave similarly with UXNavigation button.

Regarding the UXNavigationButton and UXDockButton issue, I will need to discuss this issue with the developer.

Updated: based on my discussion with the developer, this issue seems to be caused by a bug and is scheduled to be fixed in RTM. The plan is for the UXNavigationButton and UXDockButton will be similar in behavior with UXStackItem and UXDockButton.

Based on my test, you could try using WebFlyPostBackManger for a workaround in such scenario. Attached is the test page for the scenario you described using WebFlyPostBackManger. 

In my test, WebMenuBar will produce a JS error "Unspecified Error" using AJAX UpdatePanel if we try to navigate to anotehr page.

This issue has been discussed in this thread. You could continue your correspondence in the thread if you would like to know more about such scenario.

Using the client side insert row technique from Client_ProgrammaticEdit sample, I could successfully insert a new row from client side with batchupdate and grouping enabled.

Attached is the test page I am using to test the scenario. The page will require northwind.mdb database which has already provided in the WebGrid sample.

From my discussion regarding such scenario with the developer, our implementation will be similar with this article



I have already increase the bug report priority per your request and regarding the workaround, I will need to discuss it with the developer to determine if a workaround is available.

All times are GMT -5. The time now is 9:16 PM.
Previous Next