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

Allow changing gamespeed with non-numpad keys #746

Merged
merged 4 commits into from
Aug 4, 2021

Conversation

patel-nikhil
Copy link
Collaborator

Allow changing gamespeed with non-numpad +/- keys

@Krarilotus
Copy link
Collaborator

Krarilotus commented Feb 23, 2021

Please provide more in deph description which keys will be used instead, also needs a description update of the feature in the patcher itself

@Krarilotus Krarilotus added the Needs comment by author Needs comment by author label Feb 23, 2021
@patel-nikhil
Copy link
Collaborator Author

Agree, I can update the UCP description text.

As for which keys: it is the + and - keys that are not on the numpad (without shift modifier fyi).

I feel it is best to describe it as the non-numpad +/- keys, it is the most accurate way to describe it and is the equivalent of how the current behaviour is best described as using the numpad +/- keys.

I am open to suggestion, so let’s confirm this before we update the commit.

@patel-nikhil patel-nikhil added Needs comment by tester Needs comment by tester and removed Needs comment by author Needs comment by author labels Feb 25, 2021
@GRhin
Copy link

GRhin commented Feb 25, 2021

The mapping of non numpad + and - keys might be different for different keyboard languages.
Are you using key combinations? For example on a us keyboard the + is achieved by shift =, or is it the = key without shift?

@LeSpec
Copy link
Contributor

LeSpec commented Feb 25, 2021

Maybe the event keycode can clarify any confusions. From my understanding: + (=171) - (=173)
https://keycode.info/

@Krarilotus
Copy link
Collaborator

Krarilotus commented Feb 25, 2021

my own plus would be 187, minus would be 189. hm interesting

Could we have like keys that have some easy to find position? Like say ß and ´ which are on a german keyboard the ones right of the 0. it would be the ´219 and 221
But i am happy either way to get any keys for this, it should tho be a bit intuitive i would say.
So which keys are actually the ones currently mapped? Because i am not sure how i find that out...

@GRhin
Copy link

GRhin commented Feb 25, 2021 via email

@LeSpec
Copy link
Contributor

LeSpec commented Feb 25, 2021

I can't figure out what the code does, but to your question, it compares esi with 187 and 189.

@Krarilotus Krarilotus added the awaiting premature merge for dev build label Aug 3, 2021
@Krarilotus Krarilotus changed the base branch from master to development August 4, 2021 20:23
@gynt gynt merged commit 6c61300 into UnofficialCrusaderPatch:development Aug 4, 2021
Krarilotus added a commit to Krarilotus/UnofficialCrusaderPatch that referenced this pull request Dec 5, 2021
…hil/numpad"

This reverts commit 6c61300, reversing
changes made to 74c4bbe.
Krarilotus added a commit that referenced this pull request Dec 5, 2021
* Revert "Merge pull request #634 from LordHansCapon/feature/fix_assassin"

This reverts commit 21f203d, reversing
changes made to b686f90.

* Revert "Merge pull request #658 from patel-nikhil/ghost-eng"

This reverts commit b686f90, reversing
changes made to 0386db7.

* Revert "Merge pull request #688 from LordHansCapon/feature/add_restore_ai_siege_message"

This reverts commit 0386db7, reversing
changes made to d4fa4a1.

* Revert "Merge pull request #746 from patel-nikhil/numpad"

This reverts commit 6c61300, reversing
changes made to 74c4bbe.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting premature merge for dev build Needs comment by tester Needs comment by tester
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants