Chapter 12 -- User Interface Considerations

One of the main advantages of the Windows operating system is that it presents a common interface across all applications. A user with knowledge of one Windows-based application should be able to learn others more easily.

For example, most Windows-based applications have a File menu on the top left, then optional menus such as Edit and Tools, followed by Help on the right. Perhaps you think that Documents would be a better name than File, or that the Help menu should be on the left. There is nothing to prevent you from making these types of changes. But doing so might make your application less usable. If you stray from the standard format, users may have to think about the differences each time that they switch between your application and another one.

A consistent menu structure is just one way to make your application an easy-to-use working environment. Other established interface guidelines go beyond user interface issues and cover topics such as how an application behaves on different operating system platforms and whether it should allow you to run multiple instances. This lesson provides guidelines for creating applications that are compliant with the Windows architecture.


After this lesson, you will be able to:
  • Describe common user interface issues.
  • Implement OLE drag and drop functionality into applications.
  • Test for multiple instances.
  • List items you should register in the Windows registry.
  • Create a setup application.
Estimated lesson time 60 minutes



Microsoft Windows Architecture Training
Microsoft Windows Architecture for Developers Training Kit
ISBN: B00007FY9D
EAN: N/A
Year: 1998
Pages: 324

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net