Tag Info

New answers tagged

0

I want to disable the Save button until the user makes a change. Two reasons: It's redundant to have two buttons side-by-side that perform identical actions. A user might logically assume these buttons with different labels must do different things. (The little X button that closes the window and the Close button are also technically redundant, but I've ...


0

The status bar is often used for displaying the state, edit mode, or otherwise non-editable non-critical information, without cluttering the main pane. download bmml source – Wireframes created with Balsamiq Mockups If however the information is crucial because the functionality becomes crippled / very different then it's always good to alert ...


2

@Roger Attrill's answer gave me the idea to try disabled labels, which I handn't thought of before.


3

You could give the information required whilst also adding value by indicating the last time the modes were used. For example:


5

I don't think the radio buttons are a bad idea per se, but it's an explanation that itself raises new questions: if there are other modes, why can't I switch to them? It would be best to support this (or a simple label) with an explanation of the current mode and what it takes to be able to switch to the other mode. download bmml source – ...


1

I would not use radio buttons unless the user can interact with it. You can use a simple label or hyperlink (explaining what the modes are) instead. download bmml source – Wireframes created with Balsamiq Mockups You can have a overlay or a modal window pop-up when you click on the mode to explain what it is.



Top 50 recent answers are included