1 Day/Page Without Overlay Template

The 1 Day/Page template style generates a calendar showing 1 day per page. Events and tasks will be placed within their corresponding time slot rows and within the associated calendar column, rather than being overlaid into the same columns.


When creating a calendar using the 1 Day/Page Without Overlay template, the following options are provided...

Start date The start date can be typed into the box or selected using the drop-down arrow.
Number of days The total number of days to include in the output. Each day will generate to its own worksheet or page.
Timeslots  A timeslot range and interval can be specified. The output will only show times between the specified start and end values. Each row will correspond to the specified timeslot length, such as 30 minutes.
Max. columns per calendar  Each calendar data source in the generated calendar will have up to the specified number of sub-columns. These columns are used in cases where there are multiple events or tasks that occur in the same timeslot for the same calendar data source. In other words, if you set the maximum number of columns to 3, the calendar column will be able to display up to 3 overlapping events or tasks occurring in the same time slot.
Max. all-day rows  All-day events and tasks will be shown in an all-day area of the generated calendar, which is usually above the timeslot rows. This value controls how many events or tasks can be shown in the all-day area. Each event or task will take up one row.
Time Format The time format. Supported formats are 12-hour, 24-hour, Shortened, and Military. An example time is shown for each format in the drop-down list.
Show start time  When checked, event or task start times will be shown to the left of their titles.
Show end time  When checked, event or task end times will be shown to the left of their titles.
Show location  When checked, event or task locations will be included after their titles, separated by a semicolon.
Show description  When checked, descriptions will be included in event and task blocks (up to the available space).
blog comments powered by Disqus