AR
Anupama Roy
Syncfusion Team
October 12, 2005 01:07 PM UTC
Hi Yves,
I have tested the issue and I was able to see same behavior on both tab controls. (Syncfusion and .Net).I will go ahead and log a bug report based on this.Presently I am unable to provide a workaround .We will try our very best to address this issue at the earliest.
Sorry for the inconvience caused.
Regards,
Anu.
AD
Administrator
Syncfusion Team
October 13, 2005 06:53 AM UTC
Thanks for your answer. Could you please post to this forum when the bug is fixed?
AR
Anupama Roy
Syncfusion Team
October 13, 2005 07:11 AM UTC
Hi Yves,
Here is the link to track the progress of the Bug
http://www.syncfusion.com/support/issues/tools/Default.aspx?ToDo=view&questId=884
Thanks for your interest in Syncfusion products,
Best Regards,
Anu.
AD
Administrator
Syncfusion Team
January 31, 2006 07:05 PM UTC
Hi there,
We are experiencing the same problem and is getting very difficult to work around it. Is there any status of this problem or did you guys find a work around it?
Thanks,
Esmeralda
AR
Anupama Roy
Syncfusion Team
February 1, 2006 05:03 AM UTC
Hi Esmeralda,
We have not fixed this issue yet.I have notified the development team in this regard and have increased the priority of the same.We will try our very best to address this issue at the earliest.
You can track the progress of bug fix through the below given link.
questId=884
Sorry for any inconvienience caused.
Regards,
Anu.
AR
Anupama Roy
Syncfusion Team
February 1, 2006 05:12 AM UTC
Hi Esmeralda,
Here is the correct link :
questId=884
Thanks,
Anu.
AD
Administrator
Syncfusion Team
February 1, 2006 05:49 PM UTC
Hi Esmeralda,
Any ComboBox control placed on a TabPage or TabPageAdv will have this problem because of the BindingContext being different for each of the pages.
The workaround for this is to set the BindingContext of the individual TabPages to be the BindngContext of the form.
The prevents the BindingContextChanged event from being raised each time a TabPage is selected.
If you are using the Syncfusion TabControlAdv, you need to add this line of code for each TabPageAdv in the control. Example:
this.tabPageAdv1.BindingContext = this.BindingContext;
this.tabPageAdv2.BindingContext = this.BindingContext;
this.tabPageAdv3.BindingContext = this.BindingContext;
The workaround for the TabControl is also similar:
this.tabPage1.BindingContext = this.BindingContext;
this.tabPage2.BindingContext = this.BindingContext;
this.tabPage3.BindingContext = this.BindingContext;
Please let us know if this helps.
Thanks,
Davis
>Hi there,
>We are experiencing the same problem and is getting very difficult to work around it. Is there any status of this problem or did you guys find a work around it?
>
>Thanks,
>Esmeralda
VB
vbaker
February 5, 2006 08:48 PM UTC
We have tried the workaround by setting the BindingContext of each tab page to the form''s BindingContext as suggested, but then there was very erratic behavior. In short, it did not fix the problem, but actually made things worse. (Are there other things that also need to be done?)
Can you tell us how to correctly use a bound MultiColumnComboBox that has been placed on a TabPageAdv? The tab page where the combobox is located is not initially visible when the form is loaded.
We fill the ComboBox once, from a look-up table, during the form''s load event, and specify the binding of the ComboBox SelectedValue to a column in another table in a dataset. The contents of that table is cleared and re-filled from time to time based on user actions.
Given the limitations of comboboxes on tab pages, can you please advise how to do this. If this is not a recommended configuration, please tell us so that we can find an alternative (such as making the combobox unbound, for example.)
Your assistance is very much appreciated,
Van Baker
>Hi Esmeralda,
>
>Any ComboBox control placed on a TabPage or TabPageAdv will have this problem because of the BindingContext being different for each of the pages.
>
>The workaround for this is to set the BindingContext of the individual TabPages to be the BindngContext of the form.
>
>The prevents the BindingContextChanged event from being raised each time a TabPage is selected.
>
>If you are using the Syncfusion TabControlAdv, you need to add this line of code for each TabPageAdv in the control. Example:
>
> this.tabPageAdv1.BindingContext = this.BindingContext;
> this.tabPageAdv2.BindingContext = this.BindingContext;
> this.tabPageAdv3.BindingContext = this.BindingContext;
>
>The workaround for the TabControl is also similar:
>
> this.tabPage1.BindingContext = this.BindingContext;
> this.tabPage2.BindingContext = this.BindingContext;
> this.tabPage3.BindingContext = this.BindingContext;
>
>Please let us know if this helps.
>
>Thanks,
>
>Davis
>
>
>>Hi there,
>>We are experiencing the same problem and is getting very difficult to work around it. Is there any status of this problem or did you guys find a work around it?
>>
>>Thanks,
>>Esmeralda
AR
Anupama Roy
Syncfusion Team
February 6, 2006 02:59 PM UTC
Hi Van,
Since the contents of your table is cleared and filled based on user actions on MultiColumnComboBox,you can try replacing your code in
SelectionChangeCommitted Event instead of using SelectedIndexChanged event.
Please let us know if this helps you.
Thanks ,
Anu.
VB
vbaker
February 6, 2006 08:15 PM UTC
Roy,
I have no code in the SelectedIndexChanged event since we are not handling that event. The problem is that when a different tab page is selected, the combobox SelectedValue uncontrollably changes and this causes the event to fire.
This is the same problem that was reported by Yves Kurz back in October 2005, and even earlier by me in December 2004 (in a different forum: http://www.syncfusion.com/Support/forums/message.aspx?MessageID=22830).
Others and I have made many, many reports of buggy behavior with the MultiColumnComboBox and requests have been made for work-arounds to no avail. It is now clear that this control is just not ready for prime time. We will begin to remove it from our projects and are open to any suggestions for suitable alternatives.
Regards,
Van Baker
>Hi Van,
>
>Since the contents of your table is cleared and filled based on user actions on MultiColumnComboBox,you can try replacing your code in
>SelectionChangeCommitted Event instead of using SelectedIndexChanged event.
>
>Please let us know if this helps you.
>
>Thanks ,
>
>Anu.