After upgrading the controls from version 2012.3.1211.40 to the latest 2013.3.1127.40 I am seeing an issue only on one type of computer (Panasonic Toughbooks) where after you select an item from a RadDropDownList with a DropDownStyle set to DropDownList you will get a speech bubble with the value that you selected in it. If the RadDropDownList box’s style is set to DropDown, it does not exhibit the same issue and works as expected. I created a basic sample program using just the controls in the two styles with no additional code and I received the same results (see Dropdownlist attachment). Copying over the Telerik Demo programs I get the same result.
I have tried my little program on several Panasonic computers with the same results but on other non-Panasonic computers, they act normally. Any Ideas as to what may be going on since the old version of the controls worked fine.
John
8 Answers, 1 is accepted
Daniel
Thank you for writing.
We already have similar behaviour reported and it is probably a result of running an accessibility software as a Windows Narrator or JAWS on your machine. Another program that uses this accessibility interface is Visual Studio CodedUI tests functionality or some touch screens.
You can turn off these tooltips by setting the AccessibilityRequested property after displaying the RadDropDownList. For example you can do this in a form's Shown event handler:
private
void
Form1_Shown(
object
sender, EventArgs e)
//handles Form Shown event
{
this
.radDropDownList.AccessibilityRequested =
false
;
}
Another way to work around this is to use custom class which derives from RadDropDownList and disable the
accessibility there:
public
class
MyDropDownList : RadDropDownList
{
protected
override
AccessibleObject CreateAccessibilityInstance()
{
return
null
;
}
public
override
string
ThemeClassName
{
get
{
return
typeof
(RadDropDownList).FullName;
}
set
{
base
.ThemeClassName = value;
}
}
}
I hope this will be useful.
Regards,
Dimitar
Telerik
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
MyDropDownList. or (MyDropDownList as RadDropDownList). <- doesn't give me such property.
You really should repair it ASAP...
Cheers,
Kuba.
I have the same problem.
Daniel
Thanks for your response.
I tried the first option that uses the Shown event, but there was no change.
The second option of creating the custom class worked for me.
The Pansonic Toughbooks we are using do have a touch screen.
Thanks Again.
John.
Thank you all for the feedback.
For those of you that are still experience this behavior I have attached a sample project which contains an implementation of the second approach. Could you please test with it and let me know if the issue still appears. And if it does I want to kindly ask each of you to open a support thread where you can attach your custom projects and explain your specific cases. This will allow us to investigate your exact cases and determine why the workaround is no working for them.
Also, this will be fixed in the next release of ours.
Thank you in advance for your patience and cooperation.
Regards,
Dimitar
Telerik
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>
I also tried this.radDropDownList.AccessibilityRequested = false; and it did not resolve my issue.
Thank you
Thank you for writing.
I can confirm that this issue is fixed in the latest release of UI for WinForms suite. This is why I want to recommend you to upgrade to the latest version. If you experience any difficulties during the process, do not hesitate to contact us for further assistance.
Regards,
Dimitar
Telerik
Check out the new Telerik Platform - the only modular platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native apps. Register for the free online keynote and webinar to learn more about the Platform on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT).