Weird behavior in drop down

4 posts, 0 answers
  1. Dave
    Dave avatar
    9 posts
    Member since:
    Nov 2006

    Posted 01 Mar 2007 Link to this post

    This is a weird one.  No matter how I add data to the combo, it is true (binding data, manually adding items, etc).

    My problem: I am adding an item to the top of the list (text is "(unspecified)" and value is 0) and then setting the selected index property to point to this item.  Ok, all is good so far.

    Using autocomplete, I can select the item if another item is selected.  Still good.

    The user clicks the button and drops the list down.  If that item (unspecified) is current the selected item, there is no highlight on the item in the list - the highlight is on the next item in the list.  If the user scrolls up and down through the list, the item disappears although there appears to be a blank spot where the item used to be.  And no matter what, you absolutely cannot click on the item (visible or not) to select it.  When I manually add this RadComboBoxItem, I set the enabled property for the item to true just in case.

    This happens whether I step through the data table and manually add items or whether I bind the data table to the combo.  No matter what I do, the first item is just not selectable from the drop down list but can be selected ONLY if the list is not dropped and autocomplete is on suggest-append.

    So what am I missing here?

    -Dave Ferreira
  2. Georgi
    Admin
    Georgi avatar
    212 posts

    Posted 02 Mar 2007 Link to this post

    Hello David,

    This really sounds weird! We tried to reproduce this behavior, but to no avail. Please, make sure you're using the latest build (Q4 2006 SP1). If so, would you please send us a sample project in which you have used the combobox control so that we could test it locally? You can do so in a support ticket. 

    Thanks in advance.
     

    Sincerely yours,
    Georgi
    the telerik team
  3. UI for WinForms is Visual Studio 2017 Ready
  4. Dave
    Dave avatar
    9 posts
    Member since:
    Nov 2006

    Posted 02 Mar 2007 Link to this post

    Well, I solved this one except I don't really like the outcome.  I am using WindowBlinds from Stardock, and as long as it is on and there is a theme outside of the standard Windows theme, the control exhibits this behavior.  Once I switch back to the standard Windows theme AND disable WindowBlinds, everything works as it should. 

    I've tried telling WindowBlinds NOT to skin my application, and it doesn't try.  That doesn't solve the problem, though, because the behavior is still there until I turn it off.  And WindowBlinds does not change the appearance of the controls regardless of whether the application is skinned or not, which leaves me totally confused - if it isn't interacting with the combo, why does this happen when WindowBlinds is on?

    Oh well, live and learn.  Gotta figure out what to do next - all of my testers use WindowBlinds as well.

    -Dave Ferreira
  5. Dimitar Kapitanov
    Admin
    Dimitar Kapitanov avatar
    632 posts

    Posted 05 Mar 2007 Link to this post

    Hi David,

    We would kindly ask you for a stripped down version of your application project in order to figure out what the problems is. We tested the QuickStart examples of radCombobox with the latest version of WindowsBlinds and the Aries theme, but we could not reproduce the fault behavior - everything behaved as expected.

    We would need more information to proceed further with our tests. Please, send us any additional information that you believe would be helpful, such as your WindowsBlinds version, Windows platform  type (x32 or x64), the theme that you tested and possibly some screen shots. You can send us the files in a new support ticket.

    Thanks in advance.

     
    Kind regards,
    Dimitar Kapitanov
    the telerik team
Back to Top