Skip to content

Updated the Keys.None xml description to align with other "none" implementations to avoid confusion.#9203

Merged
SimonDarksideJ merged 1 commit intoMonoGame:developfrom
SimonDarksideJ:feature/simondarksidej/keys-none
Jan 27, 2026
Merged

Updated the Keys.None xml description to align with other "none" implementations to avoid confusion.#9203
SimonDarksideJ merged 1 commit intoMonoGame:developfrom
SimonDarksideJ:feature/simondarksidej/keys-none

Conversation

@SimonDarksideJ
Copy link
Contributor

Summary

It was repoted there was confusion regardind the description of Keys.None as it was different to other implementations.

On review, this has now been updated to "No Key Set" which aligns with all other "None" enum definitions, including Buttons.None

Resolves - #7826

@SimonDarksideJ SimonDarksideJ added this to the 3.8.5 milestone Jan 26, 2026
@SimonDarksideJ SimonDarksideJ merged commit 6058c78 into MonoGame:develop Jan 27, 2026
9 checks passed
@SimonDarksideJ SimonDarksideJ deleted the feature/simondarksidej/keys-none branch January 27, 2026 09:13
viniciusjarina pushed a commit to codefoco/MonoGame that referenced this pull request Jan 29, 2026
…ementations to avoid confusion. (MonoGame#9203)

# Summary

It was repoted there was confusion regardind the description of
`Keys.None` as it was different to other implementations.

On review, this has now been updated to "No Key Set" which aligns with
all other "None" enum definitions, including `Buttons.None`

Resolves - MonoGame#7826
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants