Information in this help file pertains to: eventedit.dat

When the program displays an event it uses a 'display string' to format that event. A display string is a template into which the event is infused that determines which fields are shown and how those fields are shown. This technique is described in the help file event display strings.

As explained in that help file a display string consists of clear text and field tokens. This page details the list of valid field tokens for events. A list of valid field tokens for the contact list (if registered) is available from our technical support.

As described in the referenced help file when used in a display string the field tokens must be surrounded with squiggle brackets {} which must be inside of square brackets []. Field tokens are not case sensitive implying that {Subject}, {subject}, {SUBJECT} and {SuBjeCt} all have the same effect.

Event field tokens for display strings

The following table shows each field token and its intended use. Note that the alternate field tokens are depreciated and should not be used. The alternates are included for backward compatibility only.

Other considerations

This list of fields is similar to but not the same as the list of fields recognized by the event import feature. This list of fields applies only to event display strings only.

Hidden fields are never shown in an event display string (otherwise what would be the purpose of hiding a field?). This applies to fields that are hidden by virtue of an empty prompt or by virtue of a hidden group.

The only way to change display strings is by hand editing the eventedit.dat file. There is a separate such file for each calendar, therefore, if you wish the changes to appear in all calendars, you must edit the file in each calendar folder. If you wish to customize display strings for the task list or contact list you may do so by editing the todoedit.dat or contactedit.dat respectively.