Hello,

I have logged this as a development issue.

The original release of the DotNet Framework introduced GDI Plus, which was the new way to draw using managed code. There's a lot of controversy about it, though. In theory, GDI Plus is supposed to allow you to make your text drawing more device independent. In practice, though, it makes it impossible to accurately measure the size of text.

It's also inconsistent. Text drawn with GDI Plus has different spacing between characters than text drawn with GDI.

So some controls in the DotNet Framework which are simply wrapping Windows classes, such as the TextBox control, still draw using GDI. But controls that don't wrap a Windows control, such as the Label controls, use GDI Plus. Or at least, that's how it was back in the original CLR1 of the DotNet Framework.

Since the TextBox control always renders using GDI and there's no way to make it use GDI Plus, the only way to make everything in your application behave consistently is to use GDI.

Thanks Mike!

Maybe you can shed some light on this topic in general. Why are there two rendering modes available? I read around that .NET using the GDI+, and historically used GDI? anyway, it just gives me a headache because for the most part in our application we have left the text rendering mode left as default, yet it aobviusly switches modes when your in edit mode and when your not in edit mode.

This makes the Text Jump sizes and doesn't look very good.

is there a rendering mode I should use that wouldn't stop this? I'd like all the rendering modes to be the same so nothing flashes.

Yep, I see the problem.

I am going to forward this thread over to Infragistics Developer Support so they can create a case for you and write this issue up for developer review.

move your "Mouse" I mean :)