121c121
< system will output the error dialog shown in Figure 328.
---
> system will output the error dialog shown in Figure 310.
136c136
< <p align=center> Figure 328:  Unregistered attendees error dialog.  </p>
---
> <p align=center> Figure 310:  Unregistered attendees error dialog.  </p>
206c206
< <a name="Errors from or Related to an External Email Program">
---
> <a name="Errors from an External WWW Browser">
208c208
< 2.12.4.  Errors from or Related to an External Email Program
---
> 2.12.4.  Errors from an External WWW Browser
211,230d210
< </p><p>
< Include the case where the identity of an external mailer is not known to the
< Calendar Tool.  This condition is visible to the user by a blank value in the
< Global Options dialog described in
< <a href="options.html#Global Session-Wide Options">
< Section 2.7.6.
< </a>
< 
< <a name="Errors from or Related to an External Web Browser">
< <h4>
< 2.12.5.  Errors from or Related to an External Web Browser
< </h4>
< </a>
< </p><p>
< Include the case where the identity of an external web browser is not known to
< the Calendar Tool.  This condition is visible to the user by a blank value in
< the Global Options dialog described in
< <a href="options.html#Global Session-Wide Options">
< Section 2.7.6.
< </a>
234c214
< 2.12.6.  Administrative Errors
---
> 2.12.5.  Administrative Errors
245c225
< Figure 214,
---
> Figure 215,
260c240
< 2.12.6.1.  Non-Admin Attempting to Login as Admin
---
> 2.12.5.1.  Non-Admin Attempting to Login as Admin
268c248
< 2.12.7.  Failure of Central Host Computer
---
> 2.12.6.  Failure of Central Host Computer
303c283
< The format of the central host failure notification is shown in Figure 329.
---
> The format of the central host failure notification is shown in Figure 311.
316c296
< <p align=center> Figure 329:  Central host failure notification.  </p>
---
> <p align=center> Figure 311:  Central host failure notification.  </p>
362c342
< 2.12.7.1.  Loss or Corruption of Central Host Data
---
> 2.12.6.1.  Loss or Corruption of Central Host Data
375c355
< 2.12.7.2.  Invalid repository path
---
> 2.12.6.2.  Invalid repository path
381c361
< 2.12.8.  Failure of Local User Computer or Invalidation of User Information
---
> 2.12.7.  Failure of Local User Computer or Invalidation of User Information
391,403d370
< <a name="Attempting to Connect to a Host with the Same User ID at the Same Time">
< <h4>
< 2.12.9.  Attempting to Connect to a Host with the Same User ID at the Same
< Time
< </h4>
< </a>
< 
< <a name="Options Errors">
< <h4>
< 2.12.10.  Options Errors
< </h4>
< </a>
< 
406c373
< 2.12.10.1.  Missing or Corrupted Options File
---
> 2.12.8.  Missing or Corrupted Options File
416c383
< 2.12.11.  File Errors
---
> 2.12.9.  File Errors
419,479d385
< </p><p>
< Enumerate all the file things the user can do to fuck things up while caltool
< or caltool admin are running, and what the error messages are that correspond
< to the fuckups. Here's the beginnings of this enumeration (no sure if more
< needs to be added):
< <ul>
< <li>
< delete, corrupt, or turn off write permission to an open file -- error detected
< when user attempts save
< <li>
< delete, corrupt, or turn off read permission to an unopen file -- error
< detected when user attempts open
< <li>
< delete, corrupt, or change read permission to a file listed in the host
< connection table -- error detected when user attempts connect to host
< associated with that file
< <li>
< delete, corrupt, or change read permission to the caltool user dir -- error
< detected when user attempts connect to host associated with that file
< </ul><font color=black>
< <em>Define "corrupt".</em>
< </p><p>
< Here's some fodder nuked from the File section, to be attended to (even though
< I'm pretty fucking sick of having to re-read bullshit like this as the buck
< keeps being past):
< <blockquote>
< IDiscuss what exactly happens if the user hacks (i.e., corrupts or deletes) a
< cal tool file while either caltool or admin is running, or not running for that
< matter.  The deal is we most likely need to be completely clear about exactly
< when the cal tool reads and writes its files, and thence the effect that
< external file hacking has on cal tool behavior.  It probably won't be as smart
< as Emacs is, but hey, it ain't emacs.
< </p><p>
< Enumerate exactly when a file becomes unreadable or unwritable due to external
< change, such that the dialogs cannot deal with it properly, i.e., show it as
< enabled when a concurrent external changes renders it to a state where it
< should be disabled.
< </p><p>
< Also discuss what happens if the caltool user dir or repository dir is invalid.
< This can happen by outside diddling, or with the regular-user and admin options
< that allow the "master" directories to be changed.  E.g., here's a bit about
< admin dirs from the old options section:
< <blockquote>
< If an administrator invokes the Calendar Tool Administration program with one
< or more repository directories missing or discernibly corrupted, the system
< responds with an error message as described in
< <a href="error-conditions.html#Administrative Errors">
< Section 2.12.6.
< </a>
< </blockquote>
< </blockquote>
< </p><p>
< Among other things, let the user overwrite an existing file, of either calendar
< or other type, with a confirmation-required warning before doing so.
< </p><p>
< Desribe unwritable file error.
< </p><p>
< Also make sure that the issue of missing or corrupted files is dealt with
< fully, if it's not already been done in the File section.  I think it should
< have been dealt with semantically there, so what will go here, as usual, are
< the details of what the associated error message(s) look like.
483c389
< 2.12.12.  Zero-Instance Recurring Items
---
> 2.12.10.  Zero-Instance Recurring Items
491c397
< 2.12.13.  Exceeding Item Limits
---
> 2.12.11.  Exceeding Item Limits
496c402
< system issues the error message in Figure 330.
---
> system issues the error message in Figure 312.
503c409
< <p align=center> Figure 330:  Item limit exceeded.  </p>
---
> <p align=center> Figure 312:  Item limit exceeded.  </p>
526c432
< 2.12.14.  Host Connection Failure
---
> 2.12.12.  Host Connection Failure
546,560d451
< If the file associated with the selected host does not exist
< <blockquote><pre>
< the file associated with the selected central host does not exist in the
< Calendar Tool local files directory (offering to create it or allowing user to
< select a different one might be nice, but I can live without these offers)
< </pre></blockquote>
< If the file associated with the selected host is not a valid Calendar Tool
< calendar file:
< <blockquote><pre>
< ... <em>do this (not too tough)</em>
< </pre></blockquote>
< If the connection fails during a copy operation ... .
< <br>
< <br>
< If the calendar open fails when trying to establish a connection ... .
578a470
>