Hi -
I'm a new WinClient / WinForms controls user looking for some advice from the experienced/wise ones here! Two questions I need some guidance on:
1. What's the rule of thumb when trying to decide on whether to use the inbox controls or Infragistics controls in cases that aren't black and white like the grid? For example the textbox, groupbox, label, checkbox etc. My thinking is this: use the inbox controls where possible and use the Infragistics controls ONLY when the inbox ones don't suffice? Or is it better to just use ALL the Infragistics controls thinking this might be a better way to stay with controls that will be sure to get enhancements to them down the road vs the inbox?
2. The infamous GDI issue. Seems like it might be better for consistency and performance to use GDI rendering on all controls? And if so, is there a way to set the default TextRenderingMode to GDI for all controls instead of Default for design-time besides manually doing it one-by-one? I know you can globally set it in code for runtime, but is there an installation flag that can be set somehow to avoid having to do it in code and manually in the designer? Seems like GDI is the MS recommended approach and on the forums too. No one seems to be too happy with GDI+. Thoughts?
TIA for your help!
Leigh
http://msdn.microsoft.com/en-us/library/system.windows.forms.application.setcompatibletextrenderingdefault.aspx
3rd paragraph of Remaks on GDI performance.
Thanks for your help/advice! Excited to start using the controls again. It hasn't been since "Sheridan" that I've used them... :-)
leighkendall said:How come some of the ultra editors like labels and textboxes have different heights than the inbox controls?
The default sizes are calculated based on certain font and appearance settings. So they can't be made consistent with the Inbox controls, since they have different features. If you don't like the default height, though, you can simply set AutoSize to false and then set the height on each control explicitly to whatever you want.
leighkendall said:And in some cases like the groupbox, have a darker shade of gray and slight appearance difference than the inbox?
Not sure abut this one. I'm not an expert on the GroupBox. My guess is that we are using Windows Themes and they are not. Or, we just decided to make ours look better. :)
leighkendall said:I guess this might be why you suggested being consistent and using all the Ultra controls?
Yes, that's my point exactly.
leighkendall said:Also, on the GDI - in a Mdi app, can that static prop be set once on SubMain or Main it will persist throughout?
Yes, it's application-wide.
leighkendall said:GDI/+: why is it that MS is claiming GDI is faster then GDI+? You're saying it's actually slower?
Where does Microsoft say that? I haven't heard that from them, but my guess is... if they said that, they probably meant if you are using them directly and not through the DotNet Framework's managed code.Or something along those lines.
In our experience (and by that I mean the WinForms developer team here at Infragistics), drawing text in GDI is much slower than GDI+ in DotNet. I am basing that on testing that was done a while ago, though - like when VS2003 was released. I have not done any recent testing, so it's certainly possible they have improved the performance in more recent versions of the DotNet framework. If that's the case, though, I haven't heard about it.
Mike -
Thanks for your detailed explanations - I appreciate it.
How come some of the ultra editors like labels and textboxes have different heights than the inbox controls? And in some cases like the groupbox, have a darker shade of gray and slight appearance difference than the inbox? I guess this might be why you suggested being consistent and using all the Ultra controls?
Also, on the GDI - in a Mdi app, can that static prop be set once on SubMain or Main it will persist throughout?
GDI/+: why is it that MS is claiming GDI is faster then GDI+? You're saying it's actually slower?
Hi Leigh,
leighkendall said:1. What's the rule of thumb when trying to decide on whether to use the inbox controls or Infragistics controls in cases that aren't black and white like the grid? For example the textbox, groupbox, label, checkbox etc. My thinking is this: use the inbox controls where possible and use the Infragistics controls ONLY when the inbox ones don't suffice? Or is it better to just use ALL the Infragistics controls thinking this might be a better way to stay with controls that will be sure to get enhancements to them down the road vs the inbox?
It depends on the needs of your application, in my opinion. The Infragistics editor controls like UltraTextBox and UltraComboEditor give you lots of appearance options, the ability to add buttons and dropdowns, better auto-complete support, etc.
Personally, I would use the Infragistics controls so that all of the controls in the application are consistent. But of course, I'm biased. :)
leighkendall said:Seems like it might be better for consistency and performance to use GDI rendering on all controls?
It depends on the control. For a label control, like UltraLabel, you are probably better off with GDI Plus, since the label doesn't need to go into edit mode and show any Windows controls. For a TextBox / UltraTextEditor, you may get some text shifting in GDI+ when the control enters edit mode because it will be switching from GDI+ to GDI. There are a couple of ways around this. You could set AlwaysInEditMode to true, for example. This will disable the ability to use gradients or hatch appearance styles, but those are not used all that often, anyway. And you will still get all the other benefits of the control like editor buttons.
leighkendall said:And if so, is there a way to set the default TextRenderingMode to GDI for all controls instead of Default for design-time besides manually doing it one-by-one? I know you can globally set it in code for runtime, but is there an installation flag that can be set somehow to avoid having to do it in code and manually in the designer?
There's no way to do this at design-time, because there is no object to set a property on. You have to set it at run-time on the static property:
DrawUtility.UseGDIPlusTextRendering = false;
leighkendall said:Seems like GDI is the MS recommended approach and on the forums too. No one seems to be too happy with GDI+. Thoughts?
There are a number of problems with GDI+ when it comes to rendering text. The spacing between characters changes depending on the text, and it is not possible to accurately measure text using GDI+.
GDI does not have these issues, but the down side of GDI in DotNet is that it is slower. So if you are using a lot of text on the screen, like in a WinGrid with a large screen area and lots of columns, then using GDI could become a performance concern.
But if you and your users are running on relatively fast machines, or if you are not displaying a huge amount of text, using GDI is probably the way to go.