I have a script which makes users choose from different options in a list. I want there to be three buttons; OK, Cancel and Help (display a dialog with guidance).
However, it seems that I cannot use the "buttons" parameter within a list.
So how do I add additional buttons? (with a custom name, that displays a dialogue)
Current script:
set MyList to {"A", "B", "C"}
set Chosen to
(choose from list MyList with title "Connect to"
with prompt "What do you want to connect to?"
OK button name "Connect" cancel button name "Abort" ---and help
with multiple selections allowed) as text
Unfortunately choose from list supports only two buttons.
Alternatives are a (second) standard dialog which opens the list dialog or an AppleScriptObjC app with a custom dialog window.
While choose from list only supports two buttons, you can use AppleScriptObjC to create very rich alerts/dialogs. I recommend starting with Shane Stanley's free Myriad Tables Lib. Here's an example:
To learn more, read Chapter 26:Richer Interfaces of Shane's excellent $15 book Everyday AppleScriptObjC, available here. You could also look at Dialog Toolkit on the same page. Because Cocoa alerts and dialogs provide an "accessory view", you can put many additional controls in there.
Related
Consider a modal dialog where a user can select an item from a list.
Option 1: Instantly close the modal upon selecting an item from the list.
Option 2: Have a selected state for the selected item and provide OK / Cancel buttons to confirm the selection before closing the modal.
Which of the two options is preferred from an accessibility standpoint? (considering keyboard navigation support, etc). Note that the selection is non-destructive and the user could easily re-open the modal and change the selection.
Option 2 is your best option here is some guidance related to this and the WCAG guideline
Basically do not change context, update lists etc. automatically on any type of input, you should always give the user a chance to confirm their actions.
Now the question is do you really need a modal if all the user is doing is selecting an item from a list?
Surely it would be a better UX to just have a list you can choose from (this depends on what you are doing, just thought I would point it out as you didn't give an example).
You also need to consider the fact that your modal list should present number of options, currently selected options etc. etc. Yet again these are just guesses and something to consider, it could be irrelevant.
I need to allow the user to select 1..N of a particular parameter when generating an SSRS report. According to this otherwise very helpful blog post, that's possible, but its instructions in Step 5 to "Set the Properties of both parameters" has me clawing my noggin.
What two ("both") parameters? In the Preview tab I see the dropdown list, but right-clicking doesn't afford any contextual menu items. The other ("Design") tab shows no dropdown list, of course.
So from where is the "Allow multiple values" checkbox Step 5 mentions accessible?
You get to the parameter properties in Design mode (design tab), not preview mode. Double-click on any parameter under the parameters folder in the Report Data pane. (If the Report Data pane is not visible, Ctrl-Alt-D will show it) There, under General, is where you set the Allow multiple values option.
I have some controls RadioButton,CheckBoxGroup and TextBoxes.I want to add these controls in this Dynamic Panel . And I have a Combo Box which have values 1,2,3,4,5,6. So when i select 1 from Combobox, 1 panel should display , when i select 2 from Combo box , 2 same panels should display an so on. Please help me anybody.
If you are referring to the Dynamic Forms module by DataSprings, you can create the intended behaviour by using "Question Events". You would first go into each "panel" you want to hide and click the "Hide question until forced visible by question event" checkbox. Then, go to the Question Events page and set up one event for each combobox value, with each one set to display the appropriate "panel". Several demonstrations are available here.
I have a simple question.
I have a lot of menuitems and buttons in my application. I try to remember to add ... in the caption to indicate that a modal dialog is followed.
But should I also add those dots for a non modal dialog. I try to search in Google but cannot find any clear answer. I use Win32 and Delphi.
Regards
The ... implies that some further input is required to complete the action of the menu item.
So, "Save" means that the menu item will cause the document to save, whereas "Save..." implies that the user will need to enter the name, or choose a file format or something before the file will be saved.
Typically the further input is entered in a popup modal dialog, but (a) not every modal dialog is a prompt for further information, and (b) hypothetically some other input mechanism could be used.
The '...' implies that the user will be given the opportunity to back-out of the operation.
This was in a user interface guideline book I read back in 1995, I can't seem to find a definitive confirmation online anymore.
I'd say that this depends strongly on your personal taste. I add ... whenever any new window is opened, be it modal or non-modal, to indicate to the user that he has to expect some other window to appear.
My guess is that there should be some Microsoft UI Guidelines document about that, but neither have I ever looked for something like that nor do I know of one.
I'm designing user interface and want to ask your advises how to make it more user-friendly. Please tell any suggestions and if you have ever seen implementation of something familiar please share the link.
University. There are 40+ specialities grouped into 5 faculties. User choose several he is interested in and than orders them by priority.
For example I am interested in "programming microcontrollers", "system analysis" and "experimental physic". I must find them quickly in "programming faculty", select them and then order - what I prefer most and what I prefer less then others I select.
Any ideas welcome :)
Checkboxes and radio buttons would be appropriate for this, for both websites and desktop applications.
In my case I'd use the faculty names as headers and then add the according specialities below them, prefixed by checkboxes and radio button next to each speciality, allowing the user to set the priority.
A picture is worth a thousand words:
http://i45.tinypic.com/2ex6jy0.png
I would go for the "List builder" design pattern.
The list builder contains two lists. On the left side you have the source list (ie. the complete list of faculties/specialties), and on the right side you have the source list (the items chosen by the user in prioritized order).
Between the lists you have two buttons. "Add" (arrow to the right) and "Remove" (arrow to the left), wich adds and removes items to the destination list.
In addition you put two buttons along with the destination list. These are used for rearranging the destination list.
Eg. "Move up" and "Move down" for moving the selected item up and down.
Se examples:
http://msdn.microsoft.com/en-us/library/aa511484.aspx#listBuilders
http://osdpl.fluidproject.org/designPatterns/List-Builder