NumericUpDownLib Version 3.4

Fixes and Features Added in Version 3.4

• #55 Bugfix: Format-Text must return parsed value, else value in textbox will be overwritten with "LastEditingNumericValue" if "IsUpdateValueWhenLostFocus" is enabled on lost focus

• #56 Feature optionally disable mouse wheel

This release has been authored by Jürgen Holzer 🙏

NumericUpDownLib Version 3.3.1

• #54 LastEditingNumericValue should be as same as Value when ValueChanged

NumericUpDownLib Version 3.3

#53 Fixes "FormatString not working with custom texts", "Control not scaling correctly with HorizontalAlignment set to 'Stretch'"

Fix #1: FormatString not working with custom texts

• do not put format string into "format-string-like" curly brackets if if allready looks like a format string
• Consolidate Format string handling in base class
• adapt demo application

Fix #2: Control not scaling correctly with HorizontalAlignment set to "Stretch"

• control´s grid columns were set to auto and Horizontal allignment was set to "Center". TextBlocks were set to "Left"-Alignment. This prevents control to scale correctly in "Stretch"-mode. Buttons must be right-allgined for correct scaling
• extend demo app with GridSplitters, so that scaling can be validated

FormatException was fixed in Demo tool

Regarding to Microsoft documentation format string "D" is only supported by integral types (sbyte , byte , short , ushort , int , uint , long , ulong , and char)
(see https://learn.microsoft.com/en-us/dotnet/standard/base-types/standard-numeric-format-strings)
So a different Format string must be provided here in demo tool.

This release has been authored by Jürgen Holzer 🙏

NumericUpDownLib Version 3.2

Fixes and Features Added in Version 3.2

Bug Fixes

• Add AbstractBaseUpDown MinWidth virtual property
• do not adjust the control panel length when use mouse to drap the control of displayLength

Features Added

• WaterMark support
  Use the Watermark binding to display a default string (when the user deletes all characters in the textbox portion) to hint at the expected input format.

• add support command binding
  Use the new Command binding to process the event when the user clicks on the Up/Dowm button of the UpDown Control.

This release has been authored by heartacker and Ryan Weldin 🙏

NumericUpDownLib v3.1.0.0

This release has been authored by heartacker 🙏

• addr support update value when lostfocus,Fixes #36 #38
  Please use the IsUpdateValueWhenLostFocus property.

• support align the value to left/center/right #41
  Please use the HorizontalContentAlignment property.

• add support to force trigger the ValueChanged event with ctrl+enter #39
  Please use Control+Enter to trigger a value changed event without having to actually change a value.
  This shortcut cannot be configured out.

• support disable editingTip Fixes #37 #43
  Please use the IsEnableValidatingIndicator property.

• fix: the cursor will focus to the PART_Measuring_Element by mistake #44

NumericUpDownLib Version 3.0

Features Added in Version 3.0

• Display and Edit of Hex values

• Text portion editing can be:

  • Cancelled with Escape key or can be
  • Okay'ed with Enter Key

• The Edit TextBox displays during editing a Red or Green indicator (in upper left corner) depending on whether current text is:

  • a valid number (GREEN) or
  • not valid number (RED)

• Dependency Features Added:

  • IsLargeStepEnabled
  • FormatString
  • NumberStyle

• Improved Style/Template

Thanx for contributing go to heartacker 🙏

NumericUpDownLib Version 2.4.2.2

• Fixes Issue #15 edit by keyboard and hit 'Enter key' can't raise "ValueChanged" event
• Also fixed ignoring cursor keys for increment/decrement when a modifier keys (shif, alt, ctrl) is pressed

NumericUpDownLib Version 2.4.2.1

PR #10 Do not clear focus when the control change its visibility and its not focused.

BugFix for usage of multiple UpDown controls in one app

Fixing Issue #8

Increment/decrement with mouse drags in one direction or both

• Implemented Issue #7 to allow users a configuration of whether only vertical or only horizontal mouse moves (or both) should be used to incrment/decrement a value in small/large steps.

• Fixed Issue #4 The Minimum, Maximum, and Value properties can now be set in any order (to improve support for binding) and should be applied by the control as long as:

  • MinValue is smaller equal Value
  • Value is smaller equal MaxValue

  (implimented NUnit tests to prove this point)