Shulou(Shulou.com)06/02 Report--

This article mainly introduces the VB.NET interface design skills, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand it.

VB.NET interface design 1. Form design

The quality of the form design often affects the overall image of the software, so we must first deal with the design of the form.

1. The border of the form

The default style of form borders is "Sizeable" (variable), but not all forms can use variable borders. Because users often change the size of the form intentionally or unintentionally (such as double-clicking the title bar of the window), if the form contains a large number of controls, it is very likely to cover up some of the controls or change the relative position of the controls because the form is too large. Make the user confused.

One way to solve this problem is to dynamically change the position and size of the control during the form_Resize event to maintain its relative position in the form, but the disadvantage is that when the form is too small, it is difficult to ensure the visual effect of the control. Of course, you can use the program to control the minimum size of the form, but it's easier to set the border of the form to "Fixed Single", or to "Fixed Dialog" if you don't want to provide * minimization or minimization.

2. The initial position of the form

The initial position of the form will directly affect the use of the user, especially in the multi-window environment, if the new window completely covers the previous window, the user must think that the original window is lost. It is a good choice to use cascading to arrange windows and display the process title of each window on the taskbar. When a modal form is activated, it prevents users from manipulating other forms, so you must use the modal form without using any other form at the same time, and ensure that the form is movable.

3. Use the multi-document window interface

In the multi-window interface, all forms are based on the desktop, as if there are multiple applications running, window management is more troublesome, using MDI multi-document interface will reduce the complexity of window management to *.

In a multi-document interface, there must be one and only one main document form (MDI main form). Its form region cannot place any controls other than menu components, but it can have multiple sub-forms (MDI sub-forms), that is, MDI sub-forms cannot exist independently and cannot be modal forms, they can only be active within the form area of the MDI main form. The title bar and menu bar of the sub-form can be merged with the main form; when minimized, the sub-form does not shrink to the taskbar, but to the lower-left corner of the main form; when the main form is closed, all sub-forms can be closed automatically. Making full use of the MDI interface will make the user feel that the window control is easier.

4. The arrangement of controls

Control is the most important part of the form, and its arrangement will have an important impact on the intuition and ease of use of user operations. The placement of the control is generally mounted. Rhyme? Ying? Organizes the location of controls by function.

Placing controls in different areas of the form by function makes it easier for users to find the features they need. If you put the Font and cancel buttons together and the Color and OK buttons together, the user will be confused.

On the premise of good visibility, the size of the control should be "small" as much as possible, so that the size of the form can be reduced as much as possible.

Do not place too many controls in a form that is too small.

Placing too many controls in a too small form will cause overcrowding of the form elements and make the title and text of the control difficult to read.

If possible, use icons in button controls to make the picture more vivid and make it easier for users to understand the role of the control.

Use the ToolsTip property of the control.

"ToolsTip" can add a floating prompt to the control. When the user's mouse points to the control, the prompt bar will be automatically displayed, allowing the user to immediately understand the function of the control from the text, and it will automatically disappear after a few seconds without causing visual impairment to the user.

VB.NET interface design II. Menu design

Menu is an important part of interface design. "simple, intuitive, consistent and effective" is the principle of menu design.

The following suggestions may be helpful in creating menus that meet user expectations.

The menu items are grouped by logical function, and the items that are more related to the function are grouped with a separator in the drop-down menu.

Avoid using multiple menu items with the same function in the same menu, otherwise users will be confused. Avoid using menu items without drop-down items, because orphaned menu items are no different from buttons. Clicking on such menu items and directly generating an action usually gives the user a feeling that it is too "sudden".

To make it easier for users to use, pop-up menus can be set in the relevant form or control area, especially with the right mouse button. At the same time, these pop-up menus can keep copies in the main menu. If clicking a drop-down menu item pops up a dialog box, * add "…" to the end of the menu title. (ellipsis), this is the agreement of Windows. This will make the menu more similar to the standard Windows menu and bring convenience to users who are familiar with Windows operation.

VB.NET interface design 3. Take care of the feelings of users

The user's feeling is the touchstone for testing the success of the software, including the appearance, ease of use and speed of the software.

Usually users want to see something happen when they click an icon, control, or menu item. If there is no change on the screen after a click, the user may be confused, or think that the mouse has not been pressed correctly, or simply suspect that the program is "dead". But in fact, the program may be dealing with something that takes a long time to complete. The result is either running the same program multiple times to confirm whether the mouse is pressed (which makes the situation worse), or the program is forcibly closed. This is what we do not want to see.

The solution is simple, as long as a waiting screen is displayed before starting processing, such as a message such as "data is being processed, please wait a moment." If you can display animated icons and progress bars, the effect will be better, and it will give the user the impression that the program is working "desperately" and will be finished soon.

If the startup time of the whole program is too long, it will also cause the same situation. It can be solved in a similar way: display a "flash" screen (Flash Screen), complete the startup process during the display process, and then close the "flash" screen and enter the main program (similar to the Word startup screen). It is important to note that to display the "flash" screen, * * use Sub_Main () as the entry to the program.

Some programs with many forms continue to load or unload forms at run time, and users feel very "slow". An effective way is to pre-load the commonly used forms into memory with load statements in the program startup phase (not displayed). As long as the Show method of the form is used when needed, it can be displayed immediately. Although this may increase the time it takes for the program to start and the memory requirements, the performance of the program at runtime is much faster.

In addition, users are mostly disgusted with program operations that are not under their control, so giving users the opportunity to cancel operations will be more considerate to users.

Usually, before performing a key operation, you can display a dialog box, which includes at least two buttons: "OK" and "cancel", which can give the user a chance to "go back on his promise". In the process of performing some actions that take a long time to complete (such as data replication), a cancel button can be provided without affecting data security, giving impatient users a chance to terminate the operation. You should be proficient in using DoEvents statements when designing this feature.

Thank you for reading this article carefully. I hope the article "what are the VB.NET interface design skills shared by the editor will be helpful to everyone?" at the same time, I also hope that you will support and pay attention to the industry information channel, and more related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.