1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
/*
* Motif
*
* Copyright (c) 1987-2012, The Open Group. All rights reserved.
*
* These libraries and programs are free software; you can
* redistribute them and/or modify them under the terms of the GNU
* Lesser General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option)
* any later version.
*
* These libraries and programs are distributed in the hope that
* they will be useful, but WITHOUT ANY WARRANTY; without even the
* implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
* PURPOSE. See the GNU Lesser General Public License for more
* details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with these librararies and programs; if not, write
* to the Free Software Foundation, Inc., 51 Franklin Street, Fifth
* Floor, Boston, MA 02110-1301 USA
*/
/*
* HISTORY
*/
/*
static char rcsid[] = "$XConsortium: PromptDia1.dat /main/6 1995/07/13 19:19:04 drk $"
*/
#) A Prompt Dialog will appear. The text field will contain the string
\"MessageDialog\" and the selectionLabelString will
read \"Select a Dialog:\".
#) The PromtDialog will be 200x200, this will force the Help button
to be be positioned in a row below the OK and Cancel buttons.
#) Continue to insert callbacks and continue testing.
C)
#) Click MB1 on the OK pushbutton. A message will be printed in the term
window stating what the contents of text field is, and the Apply button
will become managed.
#) Click MB1 on the Apply button. A Message Dialog will appear. It will
be positioned at (100,100). The messageString will read \"Pick a
Dialog, Any Dialog\".
#) Click MB1 on Cancel button of the Message Dialog. The Dialog will
disappear.
#) Move the cursor into the text field and use the left and right arrow keys
to move through the entry. Then, use the up and down arrow keys. Nothing
should happen.
#) Click MB1 on the Cancel button. The textString should clear and the
Apply button should become unmanaged.
C)
#) In the text field type the name of any of the following Dialogs
(InformationDialog, ErrorDialog, WarningDialog, WorkingDialog,
MessageDialog).
#) Click MB1 on the OK pushbutton. A message will be printed in the term
window stating what the contents of text field is. Also, the Apply
button will become managed.
#) Click MB1 on the Apply button. The Dialog name that you typed into the
text field will appear and will be positioned at (100,100). The
messageString will read \"Pick a Dialog, Any Dialog\".
#) Click MB1 on Cancel button of the Dialog. The Dialog will disappear.
#) Click MB1 on the Cancel button. The textString should clear and the
Apply button should become unmanaged.
#) Repeat these steps with each of the Dialogs in the list
C)
#) Click MB1 on the Help push button. A Message Dialog positioned at (50,50)
will appear. The messageString will read \"Help!!!! - Has now arrived\".
#) Press MB1 on the Cancel pushbutton of the Message Dialog. The Dialog
will disappear.
C)
#) Give the dialog window focus. The highlight (keyboard focus) should be on
the OK button.
#) Press Cancel button. The dialog is unmanaged.
C)
#) Give the dialog window focus.
#) Focus should be on the Text widget.
#) Press Cancel button. The dialog is unmanaged.
C)
#) Give the dialog window focus.
#) Normally, the focus would be on the text field. However, we have forced
the focus programmatically onto the OK button. That is where the defaultShadow
and the highlight (location cursor) should be.
E)
|
