Closed GoogleCodeExporter closed 8 years ago
Original comment by w.kowa...@gmail.com
on 7 Oct 2010 at 11:10
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
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
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
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
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
Original issue reported on code.google.com by
w.kowa...@gmail.com
on 7 Oct 2010 at 11:10