User Profile & Activity

Glenn Layaar Support
Page
of 99
Posted: November 8, 2010 5:44 AM

I have retested the sample using the scenario you mention. Unfortunately, I alsoencounter the same issue. I have submitted a new bug report for the issue. I will update this thread if I have a new information regarding this issue.

The line <add key="ISNet.WebUI.ISRes_Compressed" value="true" /> enables SmartWebResource compression. As shown in the article, it should reduce the client resource assembly file size.

Do you mind explaining in more detail on the no results remark? Did you mean client resource files is not compressed? What about the amount of data you are trying to load, if you are trying to load a large number of data you could use the suggestion in the second article to improve performance.

Another suggestion would be to update the control to the latest build, usually each new build will have some performance improvement. 

Posted: November 7, 2010 9:02 PM

Does the sample I provided in the previous post also exhibit the same issue? I did not encounter such issue when testing the page in my environment. The northwind.mdb which used in the attached sample is already provided in the WebCombo sample.

If the sample also exhibit the same issue in your environment, please make sure you have already used the latest WebCombo 4 and WebUI Framework 3, build 220 and build 756 respectively.

Posted: November 4, 2010 11:04 PM

Based on my test, WebCombo always call the LinqDataSource select operation when opening the dropdown result. In my attached sample, I set the new WhereParameter value during LinqDataSource selecting event handler.

 

The PerformBacthUpdate method already have the option to update the WebGrid UI automatically by passing true in the second parameter of the method. However, since passing True causes JS error in the previous build; as a workaround, you will need to manually call refresh method for the WebGrid to update UI properly.

Since in the latest build this issue has been fix, passing true in the second parameter does not cause JS error, passing true in the PerformBacthUpdate method will update the WebGrid UI properly.

Based on the bug report response from the developer, in order to successfully add a new row in the child table you will need to expand the parent row and use the parent row ID as the parameter for the child row creation. Attached is the sample demonstration of such scenario. 

The current definition for PerformBathUpdate method accepts 2 parameter, public bool PerformBatchUpdate(bool throwExceptionOnError, bool UpdateUI). The reported issue is passing True as UpdateUI paramater value will result in WebGrid error.

Since the UpdateUI value is false, WebGrid will not update the UI after batch update execution so we need to call the refresh method manually in order to update the UI. With the fix, UpdateUI value could be set to true and the UI will be updated properly after batch update execution.
Posted: November 3, 2010 3:03 AM

I still could not replicate the issue using the property you provided, and I believe the WebDesktop 3 build 312 is available on the WebUI Studio 2010 R1 SP1.

I have some workaround I could suggest based on the screenshot you provided. However without being able to replicate the issue on my environment I could not test the workaround myself.

In your PopUp ResultBoxWindowType solution, you could use the AdjustResultBoxLeft property and AdjustResultBoxTop property under LayoutSettings to manually modify the result box position.

In your Normal ResultBoxWindowType solution, it seems the z-index on the left pane control has greater value compared to the z-index of the WebCombo result box. Try increasing the z-Index value in the result box or decrease the z-index value in your left pane control. 

We have already provide a simple sample of WebGrid and WebCombo integration on IntegrationwithWebCombo.NET.aspx. The sample have a WebGrid and 2 WebCombo with 77 row of data. How is the performance of the sample in your environment?

Another suggestion is to update your control to the latest build if you have not done so and read the performance improvement article provided in the blog:

Rich Features in Low Client Footprint

Faster than “fastest ASP.NET Grid” and Faster than “fastest ASP.NET Grid” – Part II

The fix for the issue I refer to in my previous post is the UpdateUI parameter set to True in PerformBatchUpdate method. With the fix in the latest build, we could pass True in the UpdateUI parameter in PerformBatchUpdate method so the UI will be updated properly.

Did you find another issue when using the latest build?

All times are GMT -5. The time now is 9:21 AM.
Previous Next