We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

ComboBoxAutoComplete dies if not directly on a Form

Thread ID:

Created:

Updated:

Platform:

Replies:

40081 Jan 24,2006 03:38 PM Jan 30,2006 06:47 AM Windows Forms 4
loading
Tags: Tools
TJ
Asked On January 24, 2006 03:38 PM

Hi. I have a project with a ComboBoxAutoComplete sitting on a GradientPanel. In 4.1.0.10 (beta), that worked with no problems. In 4.1.0.50, the combo.AutoCompleteControl.EndInit() call (part of the auto-generated InitializeComponent) throws an exception because "ParentForm can not be null!". Looking at the source, I see that the real problem is that ParentForm is something other than Form. I''m guessing that''s a bug, rather than an intentional restriction. Any ideas for a workaround? I''m currently calling InitializeComponent inside a try block and replicating the bypassed code inside a catch clause, but that''s pretty inelegant. My other attempted workarounds have been foiled by the Designer''s fondness for overwriting InitializeComponent... Thanks, Tom

Administrator [Syncfusion]
Replied On January 24, 2006 04:13 PM

I think this is also preventing the Designer from loading, with a "designer loader did not provide a root component" message. If I manually change the InitializeComponent code from .ParentForm = this.gradientPanel1; to .ParentForm = this; then at least the Designer will load. (But it''ll throw away my changes...) Repeat until frustrated.

TJ
Replied On January 24, 2006 04:49 PM

Found a workaround - I switched to using a standard ComboBox. It does auto-completion too, which is all I really need this time. Thanks, Tom

Anupama Roy [Syncfusion]
Replied On January 25, 2006 07:05 AM

Hi Tom, We regret very much for the inconvienience caused. This exception occurs due to some code changes in the source inorder to implement AutoComplete.AutoPersistentDropDownSize property. We have reproduced the issue and will make the necessary changes to fix this issue. Thanks for your interest in Syncfusion products. Regards, Anu.

Kai Iske
Replied On January 30, 2006 06:47 AM

Hi, does this apply to the release version of 4.1? If not, what is the best workaround and when to expect a fix for it? I am currently migrating a huge solution over to 4.1 and it seems this is what I came across. Any help would be appreciated. Regards Kai

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;