GUI: should the button display the current state or the state that should be reached by pressing the button?

Question

GUI: should the button display the current state or the state that should be reached by pressing the button? I have seen both, and this sometimes misleads the user. what do you think?

Answer 1

The label on the button should reflect what the button does, that is, it should describe the change that the button makes.

For example, if you have a call registration system, the button should say “Close call” and the user can click it to close the call. The button should not have the label “Call is Open”, and the user clicks to change the status of the call as very intuitive, since the button effectively does the opposite of what it says on it.

In my opinion, the shortcut - and therefore the function - of a button should rarely, if ever, change. The button is supposed to look like a physical button, and usually they only do one thing. (There are a few exceptions, such as play-pause on the media player, where it is normal to change the icon / button icon, but at least it is copying the button from a real physical device.)

, , : "Open Call" "Close Call" , . , .

, , - .

Answer 2

, .

Answer 3

, "", "" " ".

, , " ", :

, ; (.. , ); - , , , , "on" "off". .

Answer 4

, . .

, . , . .

Answer 5

, .

• If a click changes the state of an object, I would suggest that the button represents the state that the entity will enter after clicking the button

• If a click invokes some functionality, the button should represent the function.

Answer 6

The appearance of a button is also the key to its state. It must conform to environmental standards, if any (for example, a chamfered edge / shadow appears when a mouse clicks on Windows).