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

GUI Improvements #39

Closed
GoogleCodeExporter opened this issue Jun 29, 2015 · 4 comments
Closed

GUI Improvements #39

GoogleCodeExporter opened this issue Jun 29, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

1. The "Back" button should always be consistently placed.  It currently
exists at top left and bottom.
2. The "Research" button should be placed near the time controls, as they
are likely to be used together.
3. Display elements that aren't active (e.g. Research while in the New Base
dialog) should be grayed out or otherwise marked as inactive.
4. The money/CPU display should remain consistent in all dialogs.

Original issue reported on code.google.com by funnyman3595 on 6 May 2008 at 2:14

@GoogleCodeExporter
Copy link
Author

Original comment by funnyman3595 on 6 May 2008 at 2:15

@GoogleCodeExporter
Copy link
Author

Why didn't the duplicate priority go away when I removed it?

Original comment by funnyman3595 on 6 May 2008 at 2:16

@GoogleCodeExporter
Copy link
Author

5. Leaving any subscreen of Knowledge drops you back to the map screen.  You 
should
be returned to the previous screen instead.

All five of these should go away when issue 11 is resolved.  3 and 5 are the 
default
behavior of the toolkit, and the rest should be resolved while converting the 
main
codebase to use it.

Original comment by funnyman3595 on 21 May 2008 at 1:23

  • Added labels: Priority-High
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

1-4 have all been fixed and will merge alongside issue 11.  5 will be fixed as 
soon
as the Knowledge screens are re-coded to use the new GUI.

Original comment by funnyman3595 on 2 Aug 2008 at 9:25

  • Changed state: Fixed

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