[Bug]: KryptonNumericUpDown.TextAlign doesn't work properly

[Ahmed-Abdelhameed]

Describe the bug
The alignment of the KryptonNumericUpDown's text doesn't work properly when the text is being edited. as shown in the gif below.

To Reproduce
As demonstrated below:

1. Add a KryptonNumericUpDown control (its text alignment should be Center by default).
2. Move the focus in and out of the control and/or start typing.

Expected behavior
The text alignment should be the same whether or not the text is being edited.

Screenshots

Desktop:

• OS: Windows 10
• Build: 2004.

Additional context
The issue happens when the TextAlign property of the internal _numericUpDown WinForms control doesn't match the text alignment set for the Krypton NUP control. This happens in two cases:

1. By default, the alignment is set to Center but _numericUpDown.TextAlign is Left. This is probably caused by the following point anyway.
2. When the .Content.TextH of a state (e.g., StateCommon) is changed, it doesn't affect the TextAlign property.

I noticed that the TextAlign property does set the _numericUpDown.TextAlign property accordingly. But since the former has a [Browsable(false)] attribute, I'm assuming it's not to be used, in favor of the TextH property (which fails to update the _numericUpDown.TextAlign property).

So, the fix should be either to update _numericUpDown.TextAlign each time TextH is changed or if TextAlign is what should be used (I doubt it), make it visible and hide TextH instead.

[PWagner1]

@Smurf-IV Would this be a similar bug as referenced in #20?

[Smurf-IV]

@Smurf-IV Would this be a similar bug as referenced in #20?

#20 is font Selected issue (Via "Krypton Selected" values not being used I suspect)

[Smurf-IV]

This has (at least) 2 issues
OnMouse leave removes the Highlight (as per #38 ) which causes the edit to change
The Edit window is a different layout / control to the numeric display, and does not always perform a proper overwrite to f the edit control area

[giduac]

Hi, (@Smurf-IV @Ahmed-Abdelhameed)

I'd like to add some findings to this that I came across when using this control.

If the keyboard-cursor is in the control and the mouse pointer is not over the control:

• Win7/8 the mouse wheel can still scroll the value up or down.
• Win10/11 the above is only possible if the mouse pointer is over the control. The keyboard focus is maintained.

This behaviour also applies to other types of controls (Listbox / ComboBox / DomainUpDown, etc.) and is there (has been changed) since Win10. This has nothing todo with the Krypton controls. Standard Winforms Controls have the same behaviour.
Run the program on W7/8 and you'll see the difference.

The KryptonNUD control does not have the ability (like the Winforms one) to position the cursor on the value with the mouse and start editing at the selected position (see video). Aligning the value left or right makes no difference.
EDIT: I tried this also on a Kdomainupdown. This control also has mainly the same erratic behaviour as the K-NUD.

DP7bHlZzOc.mp4

[Smurf-IV]

Solved initial opening point with as part of #39
@giduac Please retest when the new nightly is produced, and create separate Bugs for the points that you are mentioning - Thanks

[giduac]

@Smurf-IV
Tested with Nightly .59
KNUD control now works as it should and the cursor can be aimed and placed on the desired location.

Opened a new ticket for KDomainUpDown
#660

[Smurf-IV]

@Smurf-IV Tested with Nightly .59 KNUD control now works as it should and the cursor can be aimed and placed on the desired location.

Great

Opened a new ticket for KDomainUpDown #660

Good practice.. Thanks

[giduac]

@Smurf-IV
This can be closed then ... ??

[Smurf-IV]

It already was: