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

Not all navigation keys can be reconfigured #25

Closed
GoogleCodeExporter opened this issue May 6, 2015 · 6 comments
Closed

Not all navigation keys can be reconfigured #25

GoogleCodeExporter opened this issue May 6, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

Curently you can only configure A, B, Down, Up, Left, Right, but not others. 
Because "keyboard reset" menu alredy handles presets it may be good idea to 
replace keyboard navigation config screen with same type of screen used for 
keyboard config (but configured to set up navigations keys instead).

Original issue reported on code.google.com by w.kowa...@gmail.com on 7 Oct 2010 at 11:10

@GoogleCodeExporter
Copy link
Author

Original comment by w.kowa...@gmail.com on 7 Oct 2010 at 11:10

@GoogleCodeExporter
Copy link
Author

Maybe navigation keys should be just removed. Purpose of them was to make 
nullpomino more userfriendly, but so far they only made things more complicated.

Original comment by w.kowa...@gmail.com on 22 Oct 2010 at 6:05

@GoogleCodeExporter
Copy link
Author

After taking a look at the mess the navigation keys have caused, I'm inclined 
to agree that they're causing more problems than they're solving. So another 
vote to just eliminate them.

Original comment by Poochy.EXE on 23 Oct 2010 at 1:20

@GoogleCodeExporter
Copy link
Author

yeah this was a major issue (being forced to use the game keys to navigate) for 
me because my hard drop key doesnt correspond at all to "up" but I havent seen 
it brought up in all the Nullpomino topics on harddrop so I guess it isnt an 
issue for many people.
So I guess we can remove them although of course the best solution would be to 
fix the mess, if it's possible :)

Original comment by olivier....@gmail.com on 23 Oct 2010 at 2:15

@GoogleCodeExporter
Copy link
Author

The other solution I can think of is to use game keys in the menus, but also 
add optional keymap slots for menu-dedicated use, disallowing any overlap 
between the game and navigation keys. So for example, if you map hard drop to 
space and up to navi-up, you'd be able to press up OR space to move up in the 
menu, while you can also map hard drop to space and leave navi-up unset to use 
only space to move up in the menu.

For the time being, though, taking out all the navigation key stuff would 
definitely be an improvement. Maybe leave the navigation key config menu in but 
comment it out in the main config menu, since we might come up with a less 
messy way to implement it later.

Original comment by Poochy.EXE on 23 Oct 2010 at 5:45

@GoogleCodeExporter
Copy link
Author

ok, actually my claims in first post here are incorrect, i was bit confused but 
it kinda works like it should. But yeah, i still think navigation keys made 
thing more confusing, but let's just get feedback from users and maybe we will 
get some good suggestions what to do about them.

Original comment by w.kowa...@gmail.com on 26 Oct 2010 at 9:58

  • Changed state: Invalid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant