When you have an UltraToolbarsManager in your form, and the DockWithinContainer property is set to 'Me/this', then any standard Textbox control that is on the same form you will no longer be able to input special characters like ® (Trademark, etc.) by typing "Alt-0174" into the text box.
Soon as you remove the UltraToolbarsManager or have the DockWithinContainer property not set to 'Me/this' then you can enter the Trademark symbol via "Alt-0174" into the Textbox.
Using VS 2008, and Infragistics 2010.1 I was able to recreate a sample application that demonstrates this problem.
dmichener said: When you have an UltraToolbarsManager in your form, and the DockWithinContainer property is set to 'Me/this', then any standard Textbox control that is on the same form you will no longer be able to input special characters like ® (Trademark, etc.) by typing "Alt-0174" into the text box. Soon as you remove the UltraToolbarsManager or have the DockWithinContainer property not set to 'Me/this' then you can enter the Trademark symbol via "Alt-0174" into the Textbox. Using VS 2008, and Infragistics 2010.1 I was able to recreate a sample application that demonstrates this problem.
Can you attach the sample application to this? To attach the project use the options tab when you're replying. I tried a ton of different menu layouts to reproduce the problem and didn't have trouble at all getting the ® to show up or any symbol.
It is possible there was a bug fix for this issue after 2010.1, so you might want to check service releases available. In my test I used the 2010.2 release.
The attached VS 2008/Infragistics 2010.1 code demonstrates the problem. I originally was testing to see if the MDI Parent/Child form was part of the problem, but determined it wasn't. In the attached code, you'll find the MDI Parent form is still there, but not used. The code also has a break point in the MDI Child form_load event where the UltraToolbarsManager has the 'DockWithinContainer' property set. If you manually bypass that one line of code, the problem goes away.
Thanks,
-Dave
I had to use the version utility since I didn't have 2010.1 installed (2010.2 installed right now) and it worked without any problems. Did you check if there was any service releases that you could upgrade to?
No, I haven't tried that yet. Our current production standard is 2010.1 and I don't want to trash my development system with a test system. I will try to recreate on VM that I can refresh.
I see now that our 2010.1 Support coverage expired, and the download page doesn't list 2010.2 as being available to us...
dmichener said: I see now that our 2010.1 Support coverage expired, and the download page doesn't list 2010.2 as being available to us...
What I mean was if you visit "My Keys & Downloads", click on your 2010.1 product. It'll load up a list of available downloads for that product. Once that loads, you'll notice a "Service Releases" group box. Downloading the most current service release will give you the latest version of 2010.1 with bug fixes.
The problem is in version 9.2.2072 and 10.1.2018. The problem is solved in 10.2.1004+ and 10.3.1000+