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 interaction resides completely in menu #6

Open
zshivers opened this issue Oct 25, 2011 · 3 comments
Open

GUI interaction resides completely in menu #6

zshivers opened this issue Oct 25, 2011 · 3 comments

Comments

@zshivers
Copy link

All of the application's menu interaction is in the menu system. The user is greeted by a confusing, blank black screen upon startup. This is not a user-friendly way to handle the GUI.

Also, when entering testing mode, the menu disappears. The user must then press the Menu key again to continue with the original action.

@benjymous
Copy link

At the very least, the "find watch" dialog should be opened on first run / if no watch is paired

@ceeeKay
Copy link

ceeeKay commented Feb 2, 2012

Take the buttons on the menu and drop them onto the main screen, at the least. There is no need to put them in a menu, especially when the main app is a blank screen. I know when I first loaded it up, I thought the app was broken for a minute, since I'd never seen behavior like this.

@benjymous
Copy link

I'm in the process of improving the UI in my fork of MWM

http://t.co/v9LZlMW2

(The menu just contains About and Exit now)

garthy pushed a commit to garthy/MWM-for-Android that referenced this issue Mar 10, 2012
This is really important. Stops corrupt read messages and half read messages!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants