Figure 83: Meeting scheduling request dialog.
--- >Figure 84: Meeting scheduling request dialog.
129c129 < Figure 5: --- > Figure 6: 187,188c187,188 < < Section 2.5.2.2.1 --- > > Section . 195c195 < Figure 84 shows the scheduler having entered information for a non-recurring --- > Figure 85 shows the scheduler having entered information for a non-recurring 205c205 <Figure 84: Scheduling a staff meeting.
--- >Figure 85: Scheduling a staff meeting.
214c214 < the system displays a list of possible meeting times, as shown in Figure 85. --- > the system displays a list of possible meeting times, as shown in Figure 86. 223c223 <Figure 85: List of possible meeting times for the csstaff --- >
Figure 86: List of possible meeting times for the csstaff 233c233 < The list in Figure 85 contains all the meeting times that conform to the values --- > The list in Figure 86 contains all the meeting times that conform to the values 261,270c261,264 < earliest to latest. The default maximum number of listed items is 20, which < value can be changed as an option setting. When there are more possible times < than maximum number setting, the list is truncated based on the sorted order. < For example, if the maximum setting is 20 and there are 35 possible times, the < list contains the 20 earliest times, with the 15 times later than that < truncated from the list. <
< The minimum number of items in the list is one. When there are no conforming < possible times, the system displays an alert message instead of the list, as < discussed in the --- > earliest to latest. The default maximum number of listed items is twenty, > which value can be changed as an option setting. The minimum number of items > in the list is one. When there are no conforming possible times, the system > displays an alert message instead of the list, as discussed in the 277c271 < enabled when the user makes a list selection. For example, Figure 86 shows the --- > enabled when the user makes a list selection. For example, Figure 87 shows the 287c281 <
Figure 86: Selection in the possible meeting times list. --- >
Figure 87: Selection in the possible meeting times list. 294,295c288,289 < When the scheduler presses `Confirm ...' in Figure 86, the system < responds with the meeting confirmation dialog in Figure 87. --- > When the scheduler presses `Confirm ...' in Figure 87, the system > responds with the meeting confirmation dialog in Figure 88. 304c298 <
Figure 87: Staff meeting confirmation dialog.
--- >Figure 88: Staff meeting confirmation dialog.
318c312 < The scheduled `On' field is formated as --- > The scheduled `On field is formated as 327,328c321,322 < < Section 2.6.5.1 --- > > Section 330c324 < discusses the format of Calendar Tool host computer names. --- > describes the format of Calendar Tool host computer names. 348c342 < Figure 83 --- > Figure 84 352c346 < Figure 87 --- > Figure 88 371c365 < Figure 88 shows the scheduler having edited the meeting confirmation dialog by --- > Figure 89 shows the scheduler having edited the meeting confirmation dialog by 382c376 <Figure 88: Meeting confirmation dialog with some edits.
--- >Figure 89: Meeting confirmation dialog with some edits.
435c429 < Figure 88, --- > Figure 89, 463c457 < The resulting filled-in request dialog is shown in Figure 89. --- > The resulting filled-in request dialog is shown in Figure 90. 472c466 <Figure 89: Scheduling another meeting.
--- >Figure 90: Scheduling another meeting.
500c494 < shown in Figure 90. --- > shown in Figure 91. 509c503 <Figure 90: List of possible meeting times for the cslect --- >
Figure 91: List of possible meeting times for the cslect 517,518c511,512 < item in Figure 90 and presses `Confirm ...', whereupon the system < displays the confirmation dialog in Figure 91. --- > item in Figure 91 and presses `Confirm ...', whereupon the system > displays the confirmation dialog in Figure 92. 527c521 <
Figure 91: Lecturer meeting confirmation dialog.
--- >Figure 92: Lecturer meeting confirmation dialog.
558c552 < Figure 88 --- > Figure 89 562c556 < Figure 87. --- > Figure 88. 593c587 < and fills in the dialog as shown in Figure 92. --- > and fills in the dialog as shown in Figure 93. 602c596 <Figure 92: Scheduling a Faculty Meeting.
--- >Figure 93: Scheduling a Faculty Meeting.
612c606 < shown in Figure 93. --- > shown in Figure 94. 621c615 <Figure 93: Details of a weekly recurring schedule.
--- >Figure 94: Details of a weekly recurring schedule.
643c637 < for Mondays at 1PM, and so fills in the details dialog as shown in Figure 94. --- > for Mondays at 1PM, and so fills in the details dialog as shown in Figure 95. 652c646 <Figure 94: Weekly recurring details filled in.
--- >Figure 95: Weekly recurring details filled in.
664c658 < button, the system responds with the message shown in Figure 95. --- > button, the system responds with the message shown in Figure 96. 673c667 <Figure 95: No times found dialog.
--- >Figure 96: No times found dialog.
692c686 < `Details ...' command and changes the values as shown in Figure 96. --- > `Details ...' command and changes the values as shown in Figure 97. 701c695 <Figure 96: Weekly recurring details modified.
--- >Figure 97: Weekly recurring details modified.
712c706 < Figure 95, --- > Figure 96, 721c715 < the system displays the dialog in Figure 97. --- > the system displays the dialog in Figure 98. 730c724 <Figure 97: Meeting scheduling options.
--- >Figure 98: Meeting scheduling options.
752c746 < Figure 93. --- > Figure 94. 764c758 < The scheduler proceeds to adjust the scheduling options as shown in Figure 98, --- > The scheduler proceeds to adjust the scheduling options as shown in Figure 99, 774c768 <Figure 98: Modified meeting scheduling options.
--- >Figure 99: Modified meeting scheduling options.
781c775 < dialog. This time the system responds with the dialog shown in Figure 99. --- > dialog. This time the system responds with the dialog shown in Figure 100. 790c784 <Figure 99: Possible meeting times with one or two faculty --- >
Figure 100: Possible meeting times with one or two faculty 801c795 < Figure 98. --- > Figure 99. 829c823 < time as originally planned, as shown in Figure 100. --- > time as originally planned, as shown in Figure 101. 838c832 <
Figure 100: Selected faculty meeting time.
--- >Figure 101: Selected faculty meeting time.
862,863c856,857 < Figure 101 shows a filled-in meeting request dialog for a computer science < special colloquium; Figure 102 shows the options settings for this request. --- > Figure 102 shows a filled-in meeting request dialog for a computer science > special colloquium; Figure 103 shows the options settings for this request. 872c866 <Figure 101: Scheduling a special colloquium.
--- >Figure 102: Scheduling a special colloquium.
885c879 <Figure 102: Special colloquium options settings.
--- >Figure 103: Special colloquium options settings.
910c904 < Figure 101, --- > Figure 102, 912c906 < the system responds with the possible times list shown in Figure 103. --- > the system responds with the possible times list shown in Figure 104. 921c915 <Figure 103: Possible times for the special colloquium.
--- >Figure 104: Possible times for the special colloquium.
930c924 < Figure 104 shows the scheduler having selected user mhutchen for --- > Figure 105 shows the scheduler having selected user mhutchen for 940c934 <Figure 104: Selecting a conflicting user for the purpose of --- >
Figure 105: Selecting a conflicting user for the purpose of 948c942 < selects `View User' in Figure 104, the system displays the daily --- > selects `View User' in Figure 105, the system displays the daily 972c966 < entering the request information shown in Figure 105. --- > entering the request information shown in Figure 106. 981c975 <
Figure 105: Scheduling a tenure review meeting.
--- >Figure 106: Scheduling a tenure review meeting.
995c989 < Figure 95. --- > Figure 96. 998c992 < time range for the meeting, as shown in Figure 106. --- > time range for the meeting, as shown in Figure 107. 1007c1001 <Figure 106: Modified tenure review meeting request.
--- >Figure 107: Modified tenure review meeting request.
1013c1007 < 107. --- > 108. 1022c1016 <Figure 107: Tenure review meeting options.
--- >Figure 108: Tenure review meeting options.
1029c1023 < ...', the system responds with the result in Figure 108. --- > ...', the system responds with the result in Figure 109. 1038c1032 <Figure 108: Very long possible times list.
--- >Figure 109: Very long possible times list.
1050c1044 < find one that is acceptable and selects it, as shown in Figure 109. --- > find one that is acceptable and selects it, as shown in Figure 110. 1059c1053 <Figure 109: Long possible times list scrolled to an --- >
Figure 110: Long possible times list scrolled to an 1069c1063 < 108 --- > 109 1073c1067 < 109 --- > 110 1088c1082 < except the scheduler, with a dialog of the form shown in Figure 110. --- > except the scheduler, with a dialog of the form shown in Figure 111. 1097c1091 <
Figure 110: Meeting notification dialog.
--- >Figure 111: Meeting notification dialog.
1108c1102 < form shown in Figure 111. --- > form shown in Figure 112. 1117c1111 <Figure 111: Recurring meeting notification dialog.
--- >Figure 112: Recurring meeting notification dialog.
1137,1138c1131,1132 < presses `View ...' in Figure 110, the system responds with the meeting < information shown in Figure 112. --- > presses `View ...' in Figure 111, the system responds with the meeting > information shown in Figure 113. 1147c1141 <Figure 112: Viewing details of a meeting notification.
--- >Figure 113: Viewing details of a meeting notification.
1155c1149 < Figure 88 --- > Figure 89 1170c1164 < Figure 110 --- > Figure 111 1174c1168 < Figure 112 --- > Figure 113 1243c1237 < Figure 112, --- > Figure 113, 1246c1240 < fields, and turn off the reminder, as shown in Figure 113. --- > fields, and turn off the reminder, as shown in Figure 114. 1255c1249 <Figure 113: Notification details dialog edited.
--- >Figure 114: Notification details dialog edited.
1265c1259 < 112 --- > 113 1269c1263 < 113 --- > 114 1296c1290 < monthly calendar views, as well as in all list views. For example, Figure 114 --- > monthly calendar views, as well as in all list views. For example, Figure 115 1307c1301 <Figure 114: Two meetings displayed in penciled-in form.
--- >Figure 115: Two meetings displayed in penciled-in form.
1317c1311 < Figure 113, --- > Figure 114, 1319c1313 < the system displays the daily agenda shown in Figure 115. --- > the system displays the daily agenda shown in Figure 116. 1328c1322 <Figure 115: Accepted meeting changed from penciled in form. --- >
Figure 116: Accepted meeting changed from penciled in form. 1336c1330 < Figure 114 --- > Figure 115 1459c1453 < Figure 110, --- > Figure 111, 1462c1456 < Figure 116. --- > Figure 117. 1477c1471 <
Figure 116: Content of email meeting notification.
--- >Figure 117: Content of email meeting notification.
1601c1595 < the user with a dialog of the form shown in Figure 117. --- > the user with a dialog of the form shown in Figure 118. 1610c1604 <Figure 117: Prompting dialog for new category definition. --- >
Figure 118: Prompting dialog for new category definition. 1618c1612 < Figure 101 --- > Figure 102 1628c1622 < Figure 113, --- > Figure 114, 1635c1629 < Figure 117. --- > Figure 118. 1675c1669 < Figure 102, --- > Figure 103, 1685c1679 < shown in Figure 118. --- > shown in Figure 119. 1694c1688 <
Figure 118: Accepted meeting with non-unique identity.
--- >Figure 119: Accepted meeting with non-unique identity.
1735d1728 < 1737d1729 < 1806c1798 < being confirmed at exactly the same time from two different central hosts, the --- > being confirmed at exactly the same time from to different central hosts, the 1819,1820c1811,1812 < < Section 2.11.32, --- > > Section 2.11.26, 1827,1828c1819,1820 < < Section 2.11.32 --- > > Section 2.11.26 1830c1822 < discusses non-modal dialogs in further detail. --- > discusses non-modal dialogs in further detail.. 1876c1868 < Figure 83 --- > Figure 84 1883c1875 < 85 --- > 86 1887c1879 < 87 --- > 88 1890c1882 < Times', the system displays a dialog of the form shown in Figure 119. --- > Times', the system displays a dialog of the form shown in Figure 120. 1899c1891 <Figure 119: Scheduling temporarily blocked.
--- >Figure 120: Scheduling temporarily blocked.
1917c1909 < Times', the system displays the dialog in Figure 120. --- > Times', the system displays the dialog in Figure 121. 1926c1918 <Figure 120: Fourth blocked user.
--- >Figure 121: Fourth blocked user.
1957c1949 < dialog of the form shown in Figure 121, accompanied with an audible alert. --- > dialog of the form shown in Figure 122, accompanied with an audible alert. 1966c1958 <Figure 121: Notification to proceed with scheduling.
--- >Figure 122: Notification to proceed with scheduling.
1987c1979 < shown in Figure 122. --- > shown in Figure 123. 1996c1988 <Figure 122: Scheduling time warning.
--- >Figure 123: Scheduling time warning.
2018,2063c2010,2014 < The preceding rules for concurrent scheduling apply on a host-specific basis. < That is, two meetings cannot be scheduled at the same time on any paricular < host. However, concurrent scheduling is not prohibited among different hosts. < Further, it is possible for the same user to be connected simultaneously to two < different hosts, as described at the end of < < Section 2.6.6.1. < << Given these facts, the host-specific rules for concurrent scheduling are not < sufficient to guarantee that the `Scheduled By' and `On' < fields are sufficient as a unique identification for all scheduled meetings. < While it is not possible for two meetings to be scheduled at exactly the same < time on any single host, it is possible for this to happen on two different < hosts. Further, if the same user ID is used to gain simultaneous access to two < different hosts, it is possible for two different meetings to have the same < values for the `Scheduled By' and `On' fields. In such < cases, the value of the `Host' field is used to guarantee unique < identification of two different meetings. <
< The circumstances under which the `Host' field is necessary to < guarantee meeting uniqueness are presumably quite rare. Given the concurrent < scheduling rules described here in < < Section 2.4.1.6.9, < < plus the uniqueness rules described in < < Section 2.4.1.6.6, < < the `Host' field is only necessary to guarantee unique identification < of different meetings when all of the following conditions are true: <