Closed GoogleCodeExporter closed 8 years ago
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
This new gui really must work with keyboard. If many windows will be shown,
each one simpler with few buttons, we need to have keys
up,down,enter,backspace/esc to navigate easily and fast through them.
Original comment by Cry...@gmail.com
on 12 Oct 2011 at 5:14
I think that could be difficult with MyGUI, since it's widgets don't seem to
have a "focused with keyboard" property like most other toolkits (Qt, gtk...)
I could think of making a simple "Menu" class that handles a single window with
only buttons ("menu entries") in it, and it would keep track of the focused
menu entry and highlight it in a different color.
Or we could achieve this "Keyboard friendlyness" by setting a shortcut for
activating each menu entry and displaying it.
e.g. Start _New game | _Options | _Quit
Original comment by scrawl...@gmail.com
on 12 Oct 2011 at 7:56
This is required for championships/tutorials.
Basically a short elegant simple game menu with:
---------
(Resume Game) - if started (or continue to load last)
Single Race
Championship
Tutorial
Replays
Options
*Quit - is in corner so not needed here
---------
Then in Single Race we would have those tabs (that we know): Track, Car, Setup.
And in Options those: Screen, Graphics, View, Input, Sound, About
Keyboard navigation for game menu (Up,Down,Back/Esc,Enter) is a must (at least
for me).
Original comment by Cry...@gmail.com
on 16 Dec 2011 at 7:36
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
Gui done, testing welcome. Keyboard works.
Original comment by Cry...@gmail.com
on 16 Jan 2012 at 10:14
GUI Problems left (imo):
- championship window title is "single race"
- should show the main menu at startup, instead of the window that was active when you quit
- fix the "can't click anything" bug (sometimes appears when you click something in the main menu, then you can't click anything on the first tab and have to switch to another tab first, then everything works again)
- mouse not shown on the dialog that appears after you started a championship
Original comment by scrawl...@gmail.com
on 3 Feb 2012 at 7:32
- while in the dialog that appears when you started a championship, pressing gui toggle key (default tab) should show/hide this dialog instead of show/hide the other gui (since you can get back to this other window by pressing "Back")
Original comment by scrawl...@gmail.com
on 3 Feb 2012 at 7:34
- gui toggle while ingame should show a menu similiar to the main menu, but with added contextual buttons like "Resume game", "Restart game", "Abort championship" and such.
Original comment by scrawl...@gmail.com
on 3 Feb 2012 at 7:36
ah write with numbers, not just -
done:
- championship window title is "single race" (changes now in code)
- fix the "can't click anything" bug (by scrawl, seems fixed)
- mouse not shown on the dialog that appears after you started a championship
also added shortcuts with alt eg.
alt-T - track (single race), alt-H - championships, G graphics (options), V view, R replays, S screen, I input
the rest I find arguable or not easy (comment 15.2, 16, 17)
Original comment by Cry...@gmail.com
on 9 Feb 2012 at 12:55
about comment 17:
"Resume game" - is just pressing tab again
"Restart game" - is F4 (or F5)
"Abort championship" - what should it do ? with the scene, unload it, go back
to blue background ?
And most probably: making variable count of buttons in main menu would be awful
in code, for up/down keys and that key focus panels.
I'm thinking of adding Help in main menu (above options). it would have 3 tabs:
some general info (up,dn,enter,backspace - navigate), readme.txt text viewer,
and about tab (moved from options window).
Original comment by Cry...@gmail.com
on 9 Feb 2012 at 2:11
Help window is there. has Readme.txt, About tab with logos, and empty main tab
for some short usefull infos, not sure what.
Original comment by Cry...@gmail.com
on 23 Feb 2012 at 5:10
[deleted comment]
Original comment by Cry...@gmail.com
on 4 Mar 2012 at 7:19
Original issue reported on code.google.com by
scrawl...@gmail.com
on 21 Mar 2011 at 8:32