iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
I've got an ajax page that uses multiple webcombo controls; 5 total. The main issue I'm having is on the post back of the controls when the control returns it causes all my other dropdowns to lose their dropdown arrow (goes to a 6 for the image) and the text font jumps to something like 12-14 pt. For the initial ajax post back of the page, the controls keep their styles by using the following properties of the combos:
ddlState.AspNetAjaxSettings.UpdateControlScripts = true;ddlState.AspNetAjaxSettings.UpdateControlStyles = true;
ddlState.AspNetAjaxSettings.UpdateControlStyles = true;
I've configured each combo to use these properties. I have 3 combos that cascade from each other and this is where I start seeing the style go away; State, County, City controls. Once the state is selected and the county list gets populated on the ajax post back, the styles for all my webcombo controls goes away. For the 1 control that does not cascade to another control the styles remain.
Additionally I've tried to wrap all the calls the properties above for all my webcombos into a single method in my code behind, and call it each time I post back using ajax for each control and this doesn't seem to affect the outcome.
Any thoughts or solutions on getting this page to work as expected?
Hi Michael,
I think those properties should be set in a button click or a control which triggered postback. Also, have you tried to use 'RequireUIRefresh' ? I made a simple sample which having 5 WebCombo with a button to postback. When postback, the style still persists. If it is possible could you please modify my attached sample so it can replicate your issue? I need it to investigate your issue.Please don't hesitate to ask if you have questions.
Regards,Handy
Thanks for the reply Handy. I've added the RequiredUIRefesh to each method that is called in my postback (just to catch all) and still having the issue. I'll try to update your sample code and post back for you to investigate further.
Regards,
Michael
Handy,
The initial ajax postback works fine using :
ddlstate.AspNetAjaxSettings.UpdateControlScripts = true;ddlstate.AspNetAjaxSettings.UpdateControlStyles = true;ddlstate.RequiresUIRefresh =
ddlstate.AspNetAjaxSettings.UpdateControlStyles = true;ddlstate.RequiresUIRefresh =
Same setup for ddlCounty, and ddlCity. The issue starts up when I cascade the dropdowns so that the state selected updates the county, and county selected updates the city dropdown. Once I get to the city level the styles go away on all webcombos.
So the way the page works is:
1. First ajax post back opens the form for entry. Combos using the the properies above remain intact.
2. Seleting a state from the ddlstate web combo (onValueChanged) causes 2nd postback to update the ddlCounty county webcombo. The retrieval works fine, dropdown arrow remains but the font style of the values in the dropdown are now gone.
3. Selecting a county from the ddlCounty webcombo (onvaluechanged) causes the 3rd postback to update the ddlCity city webcombo. This is where all styles go away on all webcombos. I've added the properties above to each postback method also. I'll attempt to recreate with the northwind db that your sample uses.
When we use Ajax we see this problem from time to time. It doesn't happen on all pages and not on all webCombos on a page. I've reported this problem many times over the years. Do you happen to have the webCombos in a tabl?
Yes indeed I'm in a table. Do you see issues with this?
Hello,
I am sorry for the late reponse. Our internet connection was broken since friday. We have just back online today. So, based on what George and you said, the issue only happens if the controls inside table.For George, unfortunately, I didn't remember if I was handling this issue at the past. Maybe the other member. But for once again, could you guys help me by replicating the issue in my sample? I add a table in my last sample but still could not see the issue.
We had the same issue, any time a webcombo was inside an update panel after and async post the style would be lost and the control would no longer function. Our solution was to make a javascript call after an async postback in the EndRequestHandler event to re initialize the webcombo.
ISControl_InitializeAtlas(webComboClientID);
document.getElementById(webComboClientID).dispose = function() {{ISControl_Dispose(webComboClientID);}}}ISGetObject(webComboClientID).DoResize();}
{
ISControl_Dispose(webComboClientID);
}
ISGetObject(webComboClientID).DoResize();
Hi,
Thank you for the information.
In some scenario, we must to use the workaround but we need to ensure if there is another way or not. If it is possible, could anyone help by sending me a simple sample that replicates this issue? I could not replicate the issue in the sample I attached.
obordigital,
Do you have a sample .cs and .aspx file you can share?
Obordigital issue similars with the following issue in this thread. DoResize() is used as workaround. Please let me know if your issue also similars.
hi if u are using UpdatePanel just remove it from ur source, perhaps it will solve ur problem..
Hi Raviraj,
Thank you for suggestion. However, there are some scenarios that they need to run with Ajax. I already replied on this thread but they have not responded yet.
My apologies for the delayed response to your suggestion(s). I've tried all the suggestions on my problematic page but still have no resolution. I have worked on a smaller page using the controls and suggestions but cannot duplicate the issues I'm having. The page I'm working on is probably the largest and most complex of the application so there may be a number of factors affecting these controls. I'm going to attempt some other work arounds this weekend. Thanks again for your help and I'll post an update this weekend.
Hi Micahel,
Thank you for the update. I will wait for your response. The sample which replicates your issue is necessary to investigate your issue because we could not ensure what exactly that caused the issue. Your issue also could be different with the others.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname