I ran into an odd error and was wondering if there as a work around.
I have only seen it happen in XP but if you have a Ribbon on a form, minimize that form and then restore the window you are left with a nice grayscale box where the ribbon used to be. I just looks like the control isn't being re-drawn or something. Having said that, if while it is in this state, I right click the form from the taskbar and select "maximize" the ribbon is now displayed properly.
Is there a setting that is causing this type of issue for only XP that you know of or have seen? I searched the forms and haven't found anyone else that has had this issue.
Hi IanLudwig,
After testing this scenario on a Windows XP machine, I have been unsuccessful in producing this behavior as per your description. The closest behavior that I can think of, which can be observed with any version of the UltraToolbarsManager Ribbon would be when the form is reduced in size below the values allocated for the AutoCollapseThreshold properties.
There are two properties with this prefix, AutoCollapseThresholdVertical and AutoCollapseThresholdHorizontal. You may adjust the minimum size which collapses the Ribbon by modifying the appropriate AutoCollapseThreshold property as in the following example code.
Example code:
void Form1_Load(object sender, EventArgs e) { //Office2007Compatibility must be disabled ultraToolbarsManager1.Office2007UICompatibility = false;
//By default, the AutoCollapseThresholdVertical property is 250 pixels, this limit can be effectively removed or //altered with a custom value ultraToolbarsManager1.Ribbon.AutoCollapseThresholdVertical = 0; //By default, the AutoCollapseThresholdHorizontal property is 300 pixels, this can also be modified with a custom //value ultraToolbarsManager1.Ribbon.AutoCollapseThresholdHorizontal = 0; }
If the behavior that you are describing deviates from that produced as a result of the AutoCollapseThreshold, please provide a sample where this issue is actively reproduced that I may investigate further.
If you have any further questions in the meantime that I may assist you with, please let me know.
Sincerely,Chris KDeveloper Support EngineerInfragistics, Inc.www.infragistics.com/support
Chris-
Thanks for taking a look. I was able to figure out where it was coming from based on a very simple project created to figure this out.
The error was coming from the .isl file based around the "UseOSTheme" option. In mine (and infragistics default Office2007Black) the UseOsThemes was set to "False" BUT upon inspection of the Office2007Silver and Office2007Blue .isl files it was set to "Default". A simple change and the issue is no more.