Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not store the default value of a NumberSetting #10445

Merged
merged 1 commit into from Nov 26, 2022

Conversation

mstv
Copy link
Member

@mstv mstv commented Nov 23, 2022

Fixes #10323

Proposed changes

Screenshots

Before

NRE

After

grafik

Test methodology

  • manual

Test environment(s)

  • Git Extensions 33.33.33
  • Build 2d4c0f4
  • Git 2.38.1.windows.1
  • Microsoft Windows NT 10.0.19045.0
  • .NET 6.0.10
  • DPI 96dpi (no scaling)

Merge strategy

I agree that the maintainer squash merge this PR (if the commit message is clear).


✒️ I contribute this code under The Developer Certificate of Origin.

because NumericUpDown cannot indicate a null value
(fixup for gitextensions#9119, fixes gitextensions#10323)
@mstv mstv self-assigned this Nov 23, 2022
Copy link
Member

@gerhardol gerhardol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+0
I do not see how this fixes the problem, but I see no reason why it would be worse and I trust you...

@mstv
Copy link
Member Author

mstv commented Nov 26, 2022

I have added "Always display the default value if nothing is set (not only for "effective")" to the description.
This part solves the NRE and triggered the change for the storage part.

@mstv mstv merged commit d4d99f2 into gitextensions:master Nov 26, 2022
@ghost ghost added this to the vNext milestone Nov 26, 2022
@mstv mstv deleted the fix/10323_numbersetting branch November 26, 2022 10:51
mstv added a commit that referenced this pull request Nov 26, 2022
because NumericUpDown cannot indicate a null value
always display the default value if nothing is set (not only for "effective")
(fixup for #9119, fixes #10323)

(cherry picked from commit d4d99f2)
@RussKie RussKie linked an issue Dec 5, 2022 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants