Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
140
FormDisplayStyle RoundedSizable change the form text font
posted

Hi there,

here are a few question about using ultratoolbarsmanager on my forms:

1/ when using an ultratoolbarsmanager on a form and setting the formDisplayStyle to RoundedSizable (not showing the ribbon), my form header text displays as Bold .. (see attachment)

I was wondering if there was any chance to change this default behaviour and restore an "unbold" text instead ? I've looked into the appstylist isl files but didn't see any prop'.. I also checked and tried lots of appearances properties on the ultratoolbarsmanager but didn't find any way to ignore this bold font.

2/ when deploying my app to vista machines, it's seems the form border style (still using the ultratoolbarsmanager whith formdisplaystyle set to Roundedsizable or showing the ribbon) has a stange look ..  a little crap, in fact: the form text doesn't render very well (kind of a glow effect around the form text) and the Maximize/minimize/restore button on the right don't show all the time .. I need to double click the form header (causing a resize) to display them correctly, as if there were not drawing properly on the first paint .. is this a known problem ? Note that there is no code on my form that act on the Paint event or so on .. just a simple form with a ultratoolbarsmanager showing the ribbon..

Any help would be greatly appreciated !

Happy new year to the whole Infragistics team

François

 

 

  • 44743
    posted

    1. This is correct functionality and this is how it works in Microsoft Office 2007. You can get around this by setting the Ribbon.Caption value to a value with formatting which doesn't use bold. I think you can change this in AppStyling by setting the Font's Bold value to False on the RibbonCaptionArea role's Active role state.

    2. This sounds like a bug which had been addressed in the past. Try upgrading to the latest SR to see if it fixes this issue.