MultiColumnComboBoxElement.DropDownHeight not working

8 posts, 0 answers
  1. Jason
    Jason avatar
    2 posts
    Member since:
    Jun 2012

    Posted 11 Mar 2009 Link to this post

    I am unable to set the height of the drop down any larger than 1 header row and 3 lines using the following assignment
    ctlRadMultiColumnComboBox.MultiColumnComboBoxElement.DropDownHeight = 500.

    So is this a bug.

  2. Nick
    Admin
    Nick avatar
    767 posts

    Posted 12 Mar 2009 Link to this post

    Hello Jason,

    You are correct - this is a bug. We are going to research the issue and provide a fix in one of our future releases.
     

    All the best,
    Nick
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
  3. UI for WinForms is Visual Studio 2017 Ready
  4. Sean
    Sean avatar
    79 posts
    Member since:
    May 2007

    Posted 31 Aug 2010 Link to this post

    I am using the Q1 2010 release and setting the DropDownHeight on a radCombobox control has no effect.

    Was this bug addressed in the Q1 2010 release?  If not then can you please provide a workaround to set the drop down height?

    Thanks,
    Sean
  5. Martin Vasilev
    Admin
    Martin Vasilev avatar
    1061 posts

    Posted 03 Sep 2010 Link to this post

    Hi Sean,

    Thank you for writing.

    Actually we have addressed the drop-down height issue and in my  tests the height was applied as expected. However, there could be something specific in your scenario that causes the issue. Please, open a new support ticket and send me a small example project that demonstrates your scenario. This will help me to investigate the case in details and provide you with further assistance.

    Best wishes,
    Martin Vasilev
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  6. Sean
    Sean avatar
    79 posts
    Member since:
    May 2007

    Posted 06 Apr 2011 Link to this post

    This doesn't appear to have been fixed in Q1 2010.  However, I did find a workaround (for anyone who is interested). 

    You have to force the drop down height in the DropDownOpening event of the combobox:

    Private Sub RadCombobox1_DropDownOpening(ByVal sender As Object, ByVal args As System.ComponentModel.CancelEventArgs) Handles RadCombobox1.DropDownOpening
      
            RadCombobox1.ComboBoxElement.ComboPopupForm.Height = RadCombobox1.DropDownHeight
      
        End Sub

    Hope this helps.

    -Sean
  7. Martin Vasilev
    Admin
    Martin Vasilev avatar
    1061 posts

    Posted 11 Apr 2011 Link to this post

    Hi Sean,

    Thank you very much for sharing your work-around with us. However I highly recommend you upgrading to the latest version: Q1 2011 (2011.1.11.315). It contains numerous improvements and bug-fixes and also DropDownHeight property works as expected.

    All the best,
    Martin Vasilev
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  8. Sean
    Sean avatar
    79 posts
    Member since:
    May 2007

    Posted 12 Apr 2011 Link to this post

    Martin,
    I appreciate your suggestion, however the application that I am working on has around 35,000 lines of code.  We rely heavily on the Telerik controls, and we have had to do A LOT of customization and workarounds for bugs with the controls.  It is simply not feasible to ask your users to upgrade to the latest version every quarter when a new release comes out.  This would require several weeks worth of coding and testing from my team to ensure that everything still works as intended.  Also, it has been my experience that when a new release comes out there are other bugs that have been introduced, so then we have to find workarounds for those issues.  I suspect that a large number of your users are in a similar situation, where they can't simply upgrade every 3-6 months. 

    Overall, I think that Telerik does a great job with all the tools you provide, but that is one complaint that I have.  You end up getting "locked in" to a particular version of the controls, and due to all the workarounds (most provided by Telerik here on the Forums and through support tickets) it is very cumbersome to upgrade.

    I was just including the workaround for anyone who in the same boat as me.

    Thanks,
    Sean
  9. Martin Vasilev
    Admin
    Martin Vasilev avatar
    1061 posts

    Posted 15 Apr 2011 Link to this post

    Hello Sean,

    Thank you for your feedback.

    I agree you have some strong points here and I can understand upgrading to the latest version could be a costly process in terms of time and resources. However our target is constantly refining our products and there are vast improvements between latest version and the one you are currently using. That is why I am recommending to consider moving forward and upgrading your solution. If you decide to do that we are wiling to provide you with required support on any difficulties, which you could encounter.

    Nevertheless, I would like to thank you for sharing your work-around for the older version with the community and I am updating your Telerik points for that. Do not hesitate to contact us again if you have any other questions.

    Regards,
    Martin Vasilev
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top
UI for WinForms is Visual Studio 2017 Ready