Hi,
I am wondering what has happend to the StatusBar control after 8.3 was released?The statusbar control we use in our application was set up just perfect. The Panels where the right size (height). I could easily fit a label control with a height of 16 or more.
Now, after applying the 8.3 version of Infragistics. All of my statusbars have changed. All panels\controls innside the statusbar have a fixed size (height) of 14. And I can't seem to change it. Every time I change the height of a control (that is beeing used in a statusbarpanel), the size goes back to 14 pixels the next time I open the form.
So I have to use panels and control with a size od only 14 pixels. That means that the text innside need to be even smaller.
Is this a glitch? Or is there a way (that I do not know of) to alter the size of statusbarpanels and controls innside?
Thanks in advance
I wasn't able to reproduce this behavior. You should ensure that you have the latest hotfix installed. If you can still reproduce this issue, you should contact Developer Support so that the issue can be further investigated, especially if a regression issue has been caused in a later release.
-Matt
Hi, and thanks for your fast reply.Yes we also have the latest hotfix installed.You can try and reproduce this by adding following elements in your test. This is what our forms have (minimum):
1) Create a windows form
2) Add a UltraToolbarsManager. Set Style to Office2007. Set FormDisplayStyle to RoundedSizable. Set IsGlassSupported to False.
3) Add a UltraStatusBar component. Set Style to Office2007. 4) Add a simple UltraLabel. Set its height size to 19 and some text. (let's say this is Label1)5) Add a Panel to the UltraStatusBar. Set its Style to ControlContainer. Set SizingMode to Automatic. 6) Set Panels Control property to Label17) Run the Form. The Label1 located at the statusbar is allmost half its original height.
Ok, no problem. I'll reference this topic to developer support.
Thanks again.
I still wasn't able to reproduce this issue following your steps, so it's possible that the issue has been addressed in an internal build. Your best bet at this point is to let Developer Support know about the issue so that they can confirm whether it has truly been fixed.