One option, is to use the same Numeric Editor and validate the value user enters and round it to the nearest 100's. For that all you need to do is update the ultraNumericEditor1_ValueChanged event with one line of code as,

private void ultraNumericEditor1_ValueChanged( object sender, EventArgs e )
{
  if( ultraNumericEditor1 != null )
  {
    int nValue = SaveObject2Int32(ultraNumericEditor1.Value);
    f (nValue > 0)
    {
      DebugWriteLine(nValue.ToString());
    }
    ultraNumericEditor1.Value = Math.Round(nValue / 100d, 0) * 100;
  }
}

Thanks,
Josheela

Hi Frank, 

I haven't been able to reproduce the issue, but the drawing code we sent you is very simple and doesn't really match what the control does when it draws the characters. So I have modified the DrawFilter to draw the text exactly how the control does it so it should match up with the rest of the characters. Please try this DrawFilter and let us know if that fixes the issue. 

    public class MaskedEditDrawFilter : IUIElementDrawFilter
    {
        public bool DrawElement(DrawPhase drawPhase, ref UIElementDrawParams drawParams)
        {
            Control control = drawParams.Element.Control;

            Font fontToDispose = drawParams.AppearanceData.CreateFont(control.Font);
            Font fontToDraw = fontToDispose ?? control.Font;
            StringFormat format = (StringFormat)StringFormat.GenericTypographic.Clone();
            format.FormatFlags &= ~StringFormatFlags.FitBlackBox;
            CharacterRange[] ranges = new CharacterRange[1];
            ranges[0] = new CharacterRange(0, 1);
            format.SetMeasurableCharacterRanges(ranges);            
            format.FormatFlags &= ~StringFormatFlags.LineLimit;
            format.FormatFlags &= ~StringFormatFlags.NoWrap;
            format.FormatFlags = StringFormatFlags.NoClip;

            RectangleF rectInsideBorders = drawParams.ElementDrawingRectInsideBorders;
            
            try
            {
                format.FormatFlags |= StringFormatFlags.NoClip;

                DrawUtility.DrawString(
                    drawParams.Graphics, 
                    "0", 
                    fontToDraw, 
                    (SolidBrush)drawParams.TextBrush,
                    rectInsideBorders, 
                    format, 
                    GdiDrawStringFlags.GDIPlus);

                format.FormatFlags &= ~StringFormatFlags.NoClip;

                DrawUtility.DrawString(
                    drawParams.Graphics,
                    "0",
                    fontToDraw,
                    (SolidBrush)drawParams.TextBrush,
                    rectInsideBorders,
                    format,
                    GdiDrawStringFlags.GDIPlus);
            }
            finally
            {
                if (null != fontToDispose)
                    fontToDispose.Dispose();
            }

            return true;
        }

        public DrawPhase GetPhasesToFilter(ref UIElementDrawParams drawParams)
        {
            var displayCharUIElement = drawParams.Element as DisplayCharUIElement;
            if (null != displayCharUIElement)
            {
                if (displayCharUIElement.DisplayChar.Char == Form1.replacementChar)
                {
                    return DrawPhase.BeforeDrawForeground;
                }
            }            

            return DrawPhase.None;
        }
    }

Hi Mike,

Yes I can confirm that the new draw filter does align the last two characters on the same vertical position also with different DPI-Settings. I have tested it with DPI-Setting 125% and also 140%.  

“If the caret is set between the two zeros the spin buttons are getting disabled and a spinning is not anymore possible. We need to set first the caret in the left hand side of the two zeros then the spin buttons are getting enabled.”

Is there also a simple trick that the spin buttons are still staying enabled?

Thank you very much indeed!

Regards
Frank

Hi Frank,

Whew, I'm glad that worked, because I was out of ideas. :)

As for the spin buttons, I don't see any way to acheive that. The two zeroes in this case are literals and therefore they are not part of the number section. The spin buttons are enabled based on the context of where the caret is, and since literals can't spin, they get disabled.

The control really wasn't designed with this particular use case in mind, so even getting the two zeroes in there as literals that don't respond to the keyboard is quite a coup, in my opinion. But I think you've pretty much hit the limit of how far this approach can go.

Actually... I take that back. There is a way to do it. :)

You could turn off the built-in spin buttons and then add your own using the ButtonsRight collection: 

this.ultraMaskedEdit1.SpinButtonDisplayStyle = Infragistics.Win.SpinButtonDisplayStyle.None;
 this.ultraMaskedEdit1.ButtonsRight.Add(new SpinEditorButton());
 this.ultraMaskedEdit1.EditorSpinButtonClick += UltraMaskedEdit1_EditorSpinButtonClick;

But then you have to handle the incrementing/decrementing of the values yourself in code: 

private void UltraMaskedEdit1_EditorSpinButtonClick(object sender, SpinButtonClickEventArgs e)
 { 
 string text = this.ultraMaskedEdit1.GetText(Infragistics.Win.UltraWinMaskedEdit.MaskMode.Raw);
 int initialValue = 0;
 if (false == string.IsNullOrEmpty(text))
 initialValue = int.Parse(text);

 switch (e.ButtonType)
 {
 case SpinButtonItem.NextItem:
 this.ultraMaskedEdit1.Value = initialValue + 1;
 break;
 case SpinButtonItem.PreviousItem:
 this.ultraMaskedEdit1.Value = initialValue - 1;
 break;
 }
 }

Hi Mike,

Your recommendation with the ButtonsRight collection does work well. The last thing for a perfect solution would be closings the gap between the two last zeros. Is there a possibility to adjust the DrawFilter in that way that the gap can be closed?

I am completely aware that we shoot a little bit over the target of the normal behavior of the UltraEditMask. The end user does not really understand that we are facing a lot of pain solving his “simple” demand of stepping in increments +/-100.

Thank you so much for your help.

Regards
Frank

Hi Mike,

I changed the replacement character to an 'o' and checked it quickly on three different virtual machines. It is now more than good enough.

Thank you very much indeed for your worthful helping!     

Regards
Frank

I think that will be extremely difficult. I think the problem is that the measurement of the text is measuring the actual text of the character and then you are drawing a different character. You could try changing the replacement character to some other character and if you are lucky, you might find a character that has exactly the same width as the '0' which is being drawn. But whether there is such a character and whether that will work on all machines is something I can't be sure of. 

Another approach you could take is drawing both 0s at once. So what you would have to do in that case is that you would not draw the 0's inside the DisplayCharUIElement - you just do nothing in the DrawFilter for those elements so they draw nothing. Then you would have to use the DrawFilter to draw a string of "00" on the parent element. The challenge in that case would be lining up the 0's with the last digit before the 0. I'm not sure if that will actually work any better. 

Frankly, if it were me, I would just remove the 0's from the MaskedEditor entirely and then put some text in a label that says "Hundreds of x's" or something like that. Not ideal from the UI perspective, but a lot easier to implement. :)

I have attached the sample with the changings.