Implementation
+
+ 
+ |
+
+ 
+ |
+
+ 
+ |
+
+ 
+ |
+
+ 
+ |
+
+ 
+ |
+
+ 
+ |
+
+ 
+ |
+
-## When to use
+Follow the rules for context help.
+Implementation
+|
+
+ |
+
+
+ |
+
|
+
+ |
+
+
+ |
+
|
+
+ |
+
+
+ |
+
|
+
+ |
+
+
+ |
+
+
+
+
+
+
+
+
+
+
-* If the text is longer than 10 words:
+* For other cases, use the [help tooltip](tooltip.md#question-mark-icon-for-help-tooltips) with the question mark icon:
-For a list or tree in the master part, place the text into the detail part.
+
-{width=673}
+
-Implementation
+
-## Inline text or a tooltip
+## Tooltip
-Use **inline help text** in settings dialogs:
+Use a [tooltip](tooltip.md):
+- If the space is not enough for showing the inline help text.
+- In frequently used dialogs, tool windows, or popups. The more often a person uses an interface, the more likely they are to remember what each option does.
+- For icons or other controls that do not have a label.
-* Settings are rarely changed. Users may forget what a setting does when they use it the next time, so it makes sense to provide additional information straight away.
-* Settings dialogs are usually not constrained in space. In most cases, it is possible to fit in a help text.
+
-{width=600}
-Use a **help tooltip** if:
+## Empty state
-* A dialog is often used. The more often a person uses an interface, the more likely they are to remember what each option does.
+Fill in [empty states](empty_state.md) of tool windows, tables, trees, and other containers with:
+- a reason why the data is missing
+- an action that can fix it
+- a link to a corresponding article in the web help.
- {width=573 style=block}
- *A refactoring dialog is used more often than a settings dialog. A help tooltip is less distracting than an inline help text.*
+
-* There is no space for an inline text.
- {width=734}
+## When to use
-* The control that needs explanation is an icon or does not have a label.
-
- {width=305}
-
-## When to use context help
-
-Explain complex behavior that a short action or a setting name cannot convey clearly.
-
-{width=543}
-
-{width=380}
-
-Explain IDE-specific entities.
-
-{width=300}
-
-Provide input format requirements and examples.
-
-{width=478}
-
-Suggest alternative ways.
-
-{width=418}
-
-Warn about possible problems.
-
-{width=361}
-
-Explain limitations.
-
-{width=432}
-
-Provide quick navigation to related settings.
-
-{width=345}
-
-## When not to use
-
-Do not use context help to explain how the user interface works. If you need to explain that, consider redesigning the UI.
-
-
+ 
+ |
+
+ Explain complex behavior that a short action or a setting name cannot convey clearly. + |
||
 |
-  |
+
+ 
+ |
+
+ Provide input format requirements and examples. + |
+
+ 
+ |
+
+ Suggest alternative ways. + |
+ ||
+ 
+ |
+
+ Warn about possible issues. + |
+ ||
+ 
+ |
+
+ Explain limitations. + |
+ ||
+ 
+ |
+
+ Provide quick navigation to related settings. + |
+ ||
+ 
+ |
+
+ Explain IDE-specific entities. + |
+ 
+ |
+
+ 
+ |
+
+ 
+ |
+
+ 
+ |
+
+ 
+ |
+
+ 
+ |
+