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
We have several cases where we use unbound combo boxes and provide client-side UI features without postbacks. One issue we've run into is that when SetSelectedRowByValue is used on an unbound box with no post back, even though the value is correctly selected and set, it is NOT set in the XmlNode which causes the posted back data to be incorrect, once the user posts the page, as to the current user selection reset by SetSelectedRowByValue.
The same is true when SetValue is used. We need to have the correct value updated as right now we're having to update it ourselves by iterating through the XmlNode attributes and updating the noteTypedValue.
[EDIT] I wanted to clarify that we basically need the SetSelectedRowByValue to work the same as if the user pulled down the list and selected an item. Updating the XmlNode is not working either, i.e., the posted back data for the WebCombo control is whatever the user selected by pulling the list down. We need to be able to use the "reset" button to reset the combo box value back to its default and this is why we need this. All without any postback for this particular page.
Does the issue still occurs when using the HTML doctype? In the UnboundCombo sample you attached earlier by using HTML doctype, the issue is resolved.
The original doctype in the sample:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 4.0 Transitional//EN"><html>
Here's our current work around, however, it's not an acceptable solution due to the UI "flicker" caused by collapsing the drop down and then retracting it. We need a client-side API that does the exact same thing as the workaround please and very, very soon.
oIsCbo.SetSelectedRowByValue(keyValue); oIsCbo.ShowDropDown(); setTimeout(function() { oIsCbo.SetSelectedIndex(oIsCbo.SelectedIndex);setTimeout(function() { oIsCbo.HideDropDown();}, 200);}, 500);
Essentially we use SetSelectedRowByValue to select by key value which then also sets the correct SelectedIndex on the object. We then show the drop down, set the selected index and then close the drop down.
If there's any way you can provide that we can manually drill into the WebCombo structure and update the data "under-the-hood" we'd prefer to do that. This is why I tried the XmlNode which everthing was updated correctly but not posted back for whatever reason. You probably store the data elsewhere but I can't find where. It would be helpful if you can provide a "hook" to where we can do this.
My Test with the attached sample indicate that using the SetSelectedRowByValue already has the same behavior with user selecting from the dropdown.
After postback, the XmlNode will contain Text and Value node which indicate the selected item. For example is selected item is "Peter Schuler" from the attached sample:
<Text><![CDATA[Peter Schuler]]></Text><Value><![CDATA[2]]></Value>
The sample is run using the latest build of WebCombo 4 and WebUI Framework 3, build 219 and build 752 respectively.
Hello Glenn,
Sorry for the late reply but I only had a chance to get back to this on Friday. In the simple example it works as expected, so no problem there. However, and I don't understand why it would not, but it doesn't work in our environment.
I updated, last week, to the latest patches/fixes via Update Manager. Here are the DLL versions:
ISNet.dll - 3.0.5000.752ISNet.WebUI.dll - 3.0.5000.752ISNet.WebUI.WebCombo.dll - 4.0.7200.219I can record a flash video to show you, but I can't post it publicly so I'd have to send it via email to you. I guess send it directly to the support email and reference this thread? Thanks.
If you could not publicly post the video you could sent it to technical@intersoftpt.com and reference this thread.
Please send the video or any image if available as an attachment.
It will also be very helpful if you could modify the simple sample so it could replicate the issue in your scenario.
Hi Glenn,
Yes, I tried to duplicate the issue in the sample but was not successful.
Did you notice any difference in the settings used in the attached sample and the one used in your projects? Is there any special character used in the selected item?
If there is any and after matching the setting or data to the attached sample the issue could be replicated in the sample, perhaps you could send us the modified sample to let us replicate the issue in our environment.
Feel free to send it to technical@intersoftpt.com, similiar to the flash video, if you think the modified sample could not be shared publicly.
I haven't had a chance to record the process as I'm working on a deadline for this week so it'll be next week before I get to that.
However, I did try a custom control in the sample that derives from WebCombo and also used our implemenation of the properties, styles and skin and it all worked fine in the sample. So I'm not sure why it's not behaving the same way in our application's architecture.
I included the sample I've modified to resemble our application.
Based on the attached sample, you will need to declare the correct doctype for XHTML.
Please use this line to declare XHTML doctype in the attached sample:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 4.0 Transitional//EN"><html xmlns="http://www.w3.org/1999/xhtml">
Do you know if this will break the WebPaneManager? I believe we had to remove all the xmlns entries from our HTML tag due to incompatibility with these controls inside the WebPaneManager.
I will try it though and let you know. Thank you.
It seems that WebPaneManager has not support XHTML doctype. If you are using WebPaneManager and WebCombo, please use HTML doctype. Here is the snippet:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" ><html>
Hi Glenn. Yes, that's what we changed at the same time we removed the xmlns. Below is what I copied and pasted from our page.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" > <html>
Ah, good catch. Sorry I missed that. I should be able to test this tomorrow. Thanks again.
The issue only occurs in our application which is using the "HTML" doc type and not "XHTML" even though it works fine in the sample I attached when using either one.
Well, changing it to XHTML mucked up the entire UI. I believe the WebPaneManager doesn't support this anyway which is what mucks everything up. Right now we just can't use XHTML.
I've just finished recording the flash video of the WebCombo post back. I'll email the video in a little while with reference to this thread. Thanks.
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
Creating your account...