The Dialog object allows you to display dialogs that prompt the user for confirmation, allow them to input text strings or passwords, and select checkbox options or choose from a drop-down list. You can also use this object to display a popup menu on screen.
You can create a Dialog object from the DOpus.Dlg, Lister.Dlg, Tab.Dlg, Func.Dlg and Command.Dlg methods.
See the Example Scripts section for an example of its use.
There are two different ways to use the Dialog object. You can either:
The one-shot methods accept several parameters but are generally not as flexible as building up the dialog and then calling Show.
Property Name |
Return Type |
Description |
---|---|---|
buttons |
string |
Specifies the buttons that are displayed at the bottom of the dialog. These buttons are used to close the dialog. The Show method returns a value indicating which button was chosen (and this value is also available in the result property). Multiple button strings must be separated with vertical bar characters (|). If a button has more than one button then by definition the last one is the "cancel" button. For example: dlg.buttons =
"OK|Retry|Cancel" dlg.buttons =
"&OK|&Retry|&Cancel" dlg.buttons =
"OK|Retry+Retry All|Cancel" dlg.buttons =
"OK|Retry+Retry All=Retry All|Skip+Skip if same modified time=Skip Same
Time|Cancel" |
choices |
object:Vector(string) |
This property uses either a Vector or an array of strings to provide a list of multiple options that can be shown to the user. The list can be presented in one of three ways:
When shown as a checkbox list the dialog is resizable; you can set the initial size using the cx and cy properties (and retrieve them afterwards if you want to save the size). |
confirm |
bool |
In a text entry dialog (i.e. the max property has been specified) setting confirm to True will require that the user types the entered text again (in a second text field) to confirm it (e.g. for a password). |
cx |
int |
For script dialogs marked as resizable, this property lets you override the width of the dialog defined in the resource - although note you can't resize a dialog smaller than its initial size. |
cy |
int |
For script dialogs marked as resizable, this property lets you override the height of the dialog defined in the resource - although note you can't resize a dialog smaller than its initial size. |
defvalue |
string |
In a text entry dialog (i.e. the max property has been specified) this property allows you to initialize the text field with a default value. (Old scripts may use "default" instead of "defvalue"; this is deprecated because it does not work in JScript where "default" is a reserved keyword.) |
defid |
int |
Allows you to change the default button (i.e. the action that will occur if the user hits enter) in the dialog. Normally the first button is the default - this has a defid of 1. The second button would have a defid of 2, and so on. If a dialog has more than one button then by definition the very last button is the "cancel" button, and this has a defid of 0. |
detach |
bool |
Set to True if you want a script dialog to run in “detached” mode, where your script provides its message loop. |
disable_window |
Use this to cause the dialog to automatically disable another window
when it's displayed. The user will be unable to click or type in the
disabled window until the dialog is closed. Normally if you use this you
would set this to the same value as the window
property. | |
icon |
string or |
Displays one of several standard icons in the top-left corner of the dialog, which can be used, for example, to indicate the severity of an error condition. The valid values for this property are warning, error, info and question.
|
input |
string |
In a text entry dialog, this property returns the text string that the user entered (i.e. once the Show method has returned). |
language |
string |
Set this property to create a script dialog in a particular language (if one or more language overlays have been provided), rather than the currently selected language. |
list |
object:Vector(bool) |
In conjunction with the choices property, this will
cause the choices to be presented as a checkbox list. You can initialize
this Vector or array with the same number of items as the
choices property, and set each one to True or
False to control the default state of each checkbox. Or,
simply set this value to 0 to activate the checkbox list
without having to initialize the state of each checkbox. |
max |
int |
This property enables text entry in the dialog - a text field will be
displayed allowing the user to enter a string. Set this property to the
maximum length of the string you want the user to be able to enter (or
0 to have no limit). |
menu |
object:Vector(int) |
In conjunction with the choices property, this will cause the choices to be presented as a popup menu rather than in a dialog. The menu will be displayed at the current mouse coordinates. You can initialize this Vector or array with the same number of items as the choices property, and set each one to a value representing various flags that control the appearance of the menu item. The available flags are as follows - their values must be added together if you need to specify more than one flag per item. 1 - bold (indicates the default
item) You can also simply set this value to 0 or 1 to activate the popup menu without having to provide flags for each item (if set to 1, the top item in the menu will appear bolded).
|
message |
string |
Specifies the message text displayed in the dialog. |
opacity |
int |
For script dialogs this property retrieves or sets the current dialog opacity level, from 0 (totally transparent) to 255 (totally opaque). |
options |
collection:DialogOption |
This is a collection of five options that will be displayed as
checkboxes in the dialog. Unlike the choices /
list scrolling checkbox list, these options are displayed
as physical checkbox controls. By default the five checkboxes are
uninitialized and won't be displayed, but if you assign a label to any of
them they will be shown to the user. When the Show method returns you can obtain the state of the checkboxes using the state property of each DialogOption object. |
password |
bool |
In a text entry dialog, set this property to True to make the text entry field a password field. In a password field the characters the user enters are not displayed. |
position |
string |
When used with a script dialog this property lets you control the dialog's position on screen. Accepted values are:
Except when set to "center" the x and y properties can be used to adjust the dialog's position. |
position_fix |
bool |
By default, Opus checks the size and position of your dialog just before it opens and fixing them if they would place any of the dialog off-screen. Positioning a dialog off-screen is usually an accident caused by saving window positions on one system and restoring them on another with different monitor resolutions or arrangements. In the rare cases where you want your dialog to open off-screen, where the user cannot see some of all of it, set this property to False. |
result |
int |
This property returns the index of the button chosen by the user to
close the dialog. The left-most button is index 1, the
next button is index 2, and so on. If a dialog has more
than one button then by definition the last (right-most) button is the
"cancel" button and so this will return index
0. |
select |
bool |
In a text entry dialog, set this property to True to automatically select the contents of the input field (as specified by the defvalue property) when the dialog opens. |
selection |
int |
In a drop-down list dialog (one with the choices property set without either list or menu), this property returns the index of the item chosen from the drop-down list after the Show method returns. |
sort |
bool |
Set this property to True if the list of choices given by the choices property should be sorted alphabetically. |
template |
string |
Lets you create a script dialog. The template property can be set to the name of the script dialog to display (as defined in your script resources), or a string that contains raw XML defining the dialog. |
title |
string |
Specifies the title text of the dialog. |
top |
bool |
Set this property to True to make the dialog "top level", or False to allow it to go behind other non-top level windows. |
want_close |
bool |
Set this property to True if you want the script dialog to generate close events in your message loop when the user clicks the window close button. You'll need to close the dialog yourself using the EndDlg method. |
want_resize |
bool |
Set this property to True if you want the script dialog to generate resize events in your message loop when the user resizes the dialog. |
window |
object:Lister
|
Use this to specify the parent window of the dialog. The dialog will
appear centered over the top of the specified window. You can provide
either a Lister
or a Tab object, or
another Dialog. If you are showing this dialog in
response to the OnAboutScript event, you can also
pass the value of the AboutData.window property. |
x |
int |
Specifies the x-position of a script dialog. Use the position property to control how the position is interpreted. After the dialog has been displayed you can change this property to move the dialog around on-screen. |
y |
int |
Specifies the y-position of a script dialog. Use the position property to control how the position is interpreted. After the dialog has been displayed you can change this property to move the dialog around on-screen. |
Method Name |
Arguments |
Return Type |
Description |
---|---|---|---|
AddHotkey |
<string:name> <string:key> |
none |
Creates a hotkey (or keyboard accelerator) for the specified key combination. When the user presses this key combination in your dialog, a hotkey event will be triggered.
|
Create |
none |
none |
When creating a script dialog, calling this method creates the underlying dialog but does not display it. This lets you create the dialog and then initialize its controls before it is shown to the user. Using Create implies a detached dialog; the detach property will be set True automatically. However, you can call RunDlg afterwards if you don't need a custom message loop and just want to set up some controls before displaying the dialog. Once the dialog has been created and its controls initialized, you should call Show or RunDlg to make it visible to the user. It will also go visible at the first GetMsg call if it hasn't already been shown. |
Control |
<string:name> |
object:Control |
Returns a Control object corresponding
to one of the controls on a script dialog. The control is identified by
its name, as defined in the script dialog resource. The optional second and third parameters are only used when the control is in a tab control (that is, when it's in a dialog that's a child of another dialog). The dialog parameter specifies the name of its parent dialog. The tab parameter specifies the name of the tab control hosting the child dialog. You would only need to specify the name of the tab if you have multiple tab controls and the same dialog is hosted inside more than one of them (this would be quite a rare occurrence). Note that none of the controls will exist until Create has been called. |
DelHotkey |
<string:name> |
none |
Deletes a hotkey you previously created with the AddHotkey method. |
Drag |
collection:Item |
string |
Allows the user to drag and drop one or more files from your dialog (and drop them in another window or application). You would usually call this in response to a drag event you receive from a static or list view control. The first parameter is an Item collection (or Vector of Item objects) representing the files to be dragged. The optional second parameter lets you control which actions are available. This should be a string containing one or more of copy, move, link. The default action can be indicated by prefixing it with a * (e.g. copy,*move,link). If you don't specify this parameter the default is to only allow copy.
The string this method returns indicates the result of the drag. For a left button drag, this will be "copy", "move", "link" or "drop". For a right-button drag it will always be "drop". If the drag is cancelled it will return "cancel". |
EndDlg |
<int:result> |
none |
Ends a script dialog running in detached mode. Normally dialogs end automatically when the user clicks the close button or another button that has its Close Dialog property set to True. This method lets you end a dialog under script control. The optional parameter specifies the result code that the Dialog.result property will return. |
Folder |
<string:title> |
object:Path |
Displays a "Browse for Folder" dialog letting the user select a folder. The optional parameters are: title - specify title of the dialog A Path object is returned to indicate the folder chosen by the user. This object will have an additional result property that will be False if the user cancelled the dialog - the other normal Path properties will only be valid if result is True. |
GetMsg |
none |
object:Msg |
Returns a Msg object representing the most recent input event in a script dialog (only used in detached mode). The return value will evaluate to False when the dialog is closed, which is when you should exit your message loop. If the dialog is not already visible (because Show has not been called) then it will become visible when you first call GetMsg. |
GetString |
<string:message> |
string |
Displays a text entry dialog allowing the user to enter a string. The optional parameters are: message - specify message string in the
dialog |
KillTimer |
<string:name> |
none |
Stops the specified timer. The timer must previously have been created by a call to the SetTimer method. |
LoadPosition |
<string:id> |
none |
Restores the previously saved position of a script dialog. The position must have
previously been saved by a call to the SavePosition
method. The id string is a string that Opus can use to
identify your dialog or the script it comes from. The template name of the
dialog will be automatically appended to this. For example, you might
specify id as "kundal" - Opus would then
internally save the position of a dialog called "dialog1" as
"kundal!dialog1". Make sure you pick a string that other script
authors are unlikely to use as Opus has no other way of telling the saved
positions apart. The optional type parameter lets you control which position elements are restored - specify "pos" to only restore the position, "size" to only restore the size, or "pos,size" to restore both (this is also the default, so you can also omit the argument all together). |
Multi |
<string:title> |
collection:Item |
Displays a "Browse to Open File" dialog that lets the user select one or more files. The optional parameters are: title - specify title of the dialog A collection of Item objects is
returned to indicate the files selected by the user. The returned object
will have a result property that you should check first -
the collection of items is only valid if result returns
True. If it returns False it means the
user cancelled the dialog. |
Open |
<string:title> |
object:Item |
Displays a "Browse to Open File" dialog that lets the user select a single file. The optional parameters are: title - specify title of the dialog |
Request |
<string:message> |
int |
Displays a dialog with one or more buttons. The optional parameters are: message - specify message string in the
dialog |
RunDlg |
none |
int |
Turns a previously detached dialog into a non-detached one, by taking over and running the default message loop. The RunDlg method won't return until the dialog has closed. You might use this if you created a dialog using Create, in order to initialize its controls, but don't actually want to run an interactive message loop. The return value is the same as the object's result property, and represents the index of the close button selected by the user. If the dialog is not already visible (because neither Show nor GetMsg were called) then it will become visible when you call RunDlg. (Compatibility note: Prior to Opus 12.22, scripts needed to call Show explicitly.) |
Save |
<string:title> |
object:Path |
Displays a "Browse to Save File" dialog that lets the user select a single file or enter a new filename to save. The optional parameters are: title - The dialog's title. default - The default file selected in the dialog. (If a folder is given, it sets the dialog's starting location, but no file will be selected.) window - The dialog's parent window (a Lister or a Tab). If not specified, the Dialog object's window property will be used. (Omit the window argument entirely if you don't want to use it; the type argument, if used, works whether third or fourth.) type - A list of filetypes to populate the "Save as Type" dropdown in the save dialog. (See below.) The optional type parameter consists of one or more pairs of strings, separated by exclamation marks (!). The first string of each pair is the plain text string shown in the drop-down, and the second string of each pair is the actual file extension. You can also specify multiple extensions for the one type by separating them with semicolon. If you want the default "All files" item to be added to the list, add a # character at the start of the string. For example, #Text Files!*.txt!Doc Files!*.doc. A Path object is returned to indicate the file chosen by the user. This object will have an additional result property that will be False if the user cancelled the dialog, and the other normal Path properties will only be valid if result is True. |
SavePosition |
<string:id> |
none |
Saves the position (and size) of the dialog to your Opus configuration. The position can then be restored later on by a call to LoadPosition.
Normally you would call LoadPosition before displaying your dialog, and SavePosition after the dialog has been closed.
The id string is a string that Opus can use to identify your dialog or the script it comes from. The template name of the dialog will be automatically appended to this. For example, you might specify id as "kundal" - Opus would then internally save the position of a dialog called "dialog1" as "kundal!dialog1". Make sure you pick a string that other script authors are unlikely to use as Opus has no other way of telling the saved positions apart. |
SetTimer |
<int:period> <string:name> |
string |
Creates a timer that will generate a periodic timer event for your script. The period must be specified in milliseconds (e.g. 1000 would equal one second).
You can optionally specify a name for the timer - if you don't provide a name, one will be generated automatically (and the name of the new timer will be returned). |
Show |
none |
int |
Displays the dialog that has been pre-configured using the various
properties of this object. See the properties section above for a full
description of these. If the detach property is False, the call will not return until the dialog has been closed. The return value is the index of the button selected by the user, and this is also available in the result property once the method returns. The left-most button is index 1, the next button is index 2, and so on. If a dialog has more than one button then by definition the last (right-most) button is the "cancel" button and so this will return index 0. If the detach property is True, the call will return immediately and the return value is meaningless. You should then either run a message loop for the “detached” dialog, or call RunDlg to run the standard loop. |
SetTaskbarGroup |
<string:group> |
bool |
Used to change how custom dialogs are grouped with other Opus windows on the taskbar. Specify a group name to move the window into an alternative group, or omit the group argument to reset back to the default group. If one or more windows are moved into the same group, they will be grouped together, separate from other the default group. This only works on Windows 7 and above, and only when taskbar grouping is enabled. Group names are limited to 103 characters and will be truncated if longer. Spaces and dots in group names are automatically converted to underscores. Only works with custom script dialogs (i.e. when you are using the template property). Must be called after the dialog has been created (i.e. after Show has been called -- see the RunDlg method if you want to avoid writing your own message loop just for this). Returns true on success. |
Vars |
<string:id> |
object:Vars |
Returns a Vars object that represents the variables that are scoped to this particular dialog. This allows scripts to use variables that persist from one use of the dialog to another.
The id string is a string that Opus can use to identify your dialog or the script it comes from. The template name of the dialog will be automatically appended to this. For example, you might specify id as "kundal" - Opus would then internally save these variables for a dialog called "dialog1" as "kundal!dialog1". Make sure you pick a string that other script authors are unlikely to use as Opus has no other way of telling the saved variables apart. |
WatchTab |
<object:Tab> |
bool |
Allows a script dialog to monitor events in a folder tab. You will receive notifications of the requested events through your message loop.
The tab parameter specifies the Tab you want to watch. The events string is a comma-separated list of events you want to watch for. The id string is an optional parameter; it lets you assign your own ID to the tab to make it easier to tell where events are coming from (if you're monitoring multiple tabs, for instance).
These are the events you can watch for are. Note that some are equivalent to the existing script events (e.g. OnActivateTab):
Once notification has been established you will be notified of all requested events when they occur. Note that no specific information is sent with notifications - e.g. for the "change" event, you aren't told which items have changed, only that something has.
You will receive notification events in your message loop. The various properties of the Msg object let you determine what happened.
The Msg.event property will be set to tab for notifications from a watched folder tab.
You can change the events you're monitoring for by calling the WatchTab method again with the same tab and new event list.
To stop monitoring an existing tab, call WatchTab with the second parameter set to stop. Monitoring is automatically cancelled if your dialog closes (and also if the tab closes).
|