Timeline for Disabling a feature until a button is pressed
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 30, 2022 at 18:26 | history | edited | Danielillo | CC BY-SA 4.0 |
added 265 characters in body
|
| Aug 30, 2022 at 18:25 | comment | added | Danielillo | Answer updated.- | |
| Aug 30, 2022 at 18:20 | comment | added | Gene | @Danielillo So what youre saying is, as long as i follow these principles/laws, the user should be able to interpret the buttons as being related to one another? | |
| Aug 30, 2022 at 16:51 | comment | added | Danielillo | As you say, presumably. In the example image there are only four buttons, only the OP knows what's around them. If above those buttons there is a working area, and to the left and right more rectangular blue and gray buttons, none of the examples exposed in my answer are fulfilled. That's why at the beginning of my answer I put: in context. | |
| Aug 30, 2022 at 16:27 | comment | added | maxathousand | So, what is your suggestion to OP's problem? Presumably, OP has already implemented your "proximity" example. Could you elaborate on whether or not you feel the current design works as illustrated, or what you think could be done to improve upon it? These examples are nice, but they lack any explanation or application to OP's situation. | |
| Aug 30, 2022 at 5:24 | history | answered | Danielillo | CC BY-SA 4.0 |