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.
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
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.
We have the same problem with 2009.2. Does anyone has a solutions/workaround?