Hello,

I would like to know the way we can improve our performance in a VWG application.

We have this problem: We are developing a solution that has some user controls displayed into modal windows (with showDialog option). We have several problems with TextBoxes and the way VWG handles its events. In a special case we have designed a table with tablelayoutpanel that has one column with checkboxes, and two other columns with textboxes (dinamically generated). When handling textboxes events, sometimes it happens that when a lostfocus event is processed on a textbox if you check a checkbox this event is not detected serverside and no longer you can recognize the check into the CheckBox. We have tried with VWG 6.1.4 and VWG 6.3 and this issue still remains. We are thinking about buying a commercial licence but we must know if this issue is going to be solved or if there is any solution we can apply.

We think that this issue has to do with AJAX event handling of TextBoxes. Perhaps both events are sent at the same time and only one is processed? Has anyone detected this behaviour?

Any help please?

Thanks,

Rubén

Hi Palli and thanks for your help,

We have detected that if the load of events of the application is high there are looses of events. This issue mainly occurs with Button Clicks but it happens also with other controls such as CheckBoxes. When the textbox looses focus it sends by Ajax a ValueChange event. If there is a high load, after this event the next is not sent.

We have sent you an example app to reproduce this problem.

Rubén

Hello Rubén,

Regarding the first problem you mentioned about the MessageBox displaying only 20 rows from a certain amount:
I thoroughly tested this scenario, and found to my surprise that this happens when more than 30 rows exist in the table.
I took the string that is supposed to be written to the MessageBox with 31 rows to a different application that only dislpays that message and again it only diaplyed 20. I then migrated that minimal application to MS Winforms and I did exactly the same.

Since this is MS Winforms behavior, even if it is a bug that they have, we must have it also, for compatibility reasons.

I uploaded the applications I created so you could see this for yourself. Please get it from here. If the link is broken, you can find the application in this issue here, by searching for thread number 25471.


Regarding the second problem, I could not reproduce it. Tested on VWG v6.3.7.

Regards,

Ori Cohen
Support Manager, the Visual WebGui team