1. Use some information that is meaningless to users. Especially when the program has an error, some error messages often display some error messages to tell the user. But there are many
In the order, it is displayed some information about the programmer is very helpful and the user is inexplicably. Users often don't know what to do next. So in display
When information is information, you must use the language that you can understand and make a clear instruction based on the situation at the time; and write the information useful for programmers to the log file.
2. No use or abuse ... tag. "..." tag usually appears in the menu or button text, indicating that the current command will not be executed immediately, but to pop up a window
Enter more information to execute commands, such as "save as ..."; without ... tagged menu or button, indicating that this command will be executed immediately. There is no programmer
Follow this specification, where the added place is not added, the place where it is not added is abused. Be sure to pay attention to this problem.
3. Not uniform when using the colon. In a program, you will often see some tags, add colon, but there are no additions to the label, and even sometimes it will be in one window.
To this case. This is caused by the initial project group without uniform opinions or programmers did not pay attention to this problem.
4. Use the same title in a different window or the window title that appears to call it does not match the command called. This is also the problem to pay attention to.
