|
|
271.
|
|
|
The tooltip class changes the screen when a button is hovered.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_actions.rst:124
|
|
|
272.
|
|
|
A tooltip object can be used to define a portion of a screen that is updated when the mouse hovers an area.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/tooltips:5
|
|
|
273.
|
|
|
A tooltip object has a ``value`` field, which is set to the `default` value passed to the constructor when the tooltip is created. When a button using an action created by the tooltip is hovered, the value field changes to the value associated with the action.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/tooltips:8
|
|
|
274.
|
|
|
Returns an action that is generally used as the hovered property of a button. When the button is hovered, the value field of this tooltip is set to `value`. When the buttton loses focus, the value field of this tooltip reverts to the default.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/tooltips:15
|
|
|
275.
|
|
|
When using a tooltip with a screen, the usual behavior is to create a tooltip object in a default statement. The value of the tooltip and the action method can then be used within the screen. The order of use within a screen doesn't matter - it's possible to use the value before an action is used.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_actions.rst:128
|
|
|
276.
|
|
|
Tooltips can take on any value. While in the example below we use the text statement to display a string on the screen, it's also possible to use the add statement to add a displayable. More complex behavior is also possible.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_actions.rst:134
|
