Hey guys,
I'm seeing a couple of issues I need to work through around setting up our combo boxes. Here are our requirements:
I suppose a workaround for some of this tabbing behavior is that I COULD allow focus to be had on readonly fields but manually handle the tab behavior to continue to skip over readonly fields.
Thanks!
Adam.g
I'm seeing a couple of issues I need to work through around setting up our combo boxes. Here are our requirements:
- We're using the RadComboBox as IsEditable though it will not accept custom text. This is more for aesthetics. When we set the IsReadOnly="True", I believe we see that the textbox portion of dropdown is appropriately readonly. However, the dropdown button is still enabled and you can still open the items. I suppose I can see how this would be desirable for some people, but is there a different way to signal that the control itself should be readonly, not just the editable textbox?
- We need to set IsReadOnly and not IsEnabled because it still allows us to select and copy the text of the selected item. However, it also necessary that we do not focus or otherwise allow the user to tab into readonly fields since that wastes their time. With this, we see that for some reason a control needs focus in order for text to be selectable. This is most apparent with the silverlight textbox. Which brings me to an overall issue that I think I'm seeing with the combo box...
- At least with the settings we use in the combo box, IsTabStop="False" does not seem to work to stop the tab from giving the control focus. Is this a known bug?
I suppose a workaround for some of this tabbing behavior is that I COULD allow focus to be had on readonly fields but manually handle the tab behavior to continue to skip over readonly fields.
Thanks!
Adam.g