I think that initially you should display all three buttons, all at the bottom right of the dialog, where the primary is "load into simulator", and it's disabled as long as no valid code has been assembled. If he didn't make any changes, then he can only Load or Cancel, but there's nothing new to assemble. If the user made changes, then he should assemble the text again, so Load is disabled. If I understood correctly, there's no point where both Assemble and Load are enabled. By only displaying it after the user has generated valid code you're breaking the process down into steps, basically making this a kind of wizard, but not supporting it by a wizard-like layout. The primary button is "load into simulator", because that's the one that lets you close the dialog and proceed. Your dialog actually has three buttons - cancel, assemble, load into simulator. It would probably be weird to make the "Assemble" button no longer a primary action after being pressed-to change its primary status at runtime-right?.After the user assembles code, there really are two primary actions either of the two buttons I've currently marked primary is a perfectly plausible next step.Before the user first assembles code, "Assemble" certainly is the primary action.The green success alert only appears after a user submits some valid code into the textbox and presses "Assemble." Here's a picture to demonstrate what I mean. Once the user enters text and presses "Assemble," they have the option to either make changes and "Assemble" again, or to complete the action (closing the modal dialog and doing processing).ĭoes it make sense for the button to complete the action to also be primary? The latter button is the primary action (in Bootstrap. Initially, there are two buttons: "Cancel" and "Assemble." ![]() ![]() I have a dialog that allows the user to enter text to be processed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |