An Appointment object maintains information regarding a task for a particular date and time. The start and end of the appointment are stored in the or respectively. To change the start of the appointment without changing the duration, use the method.

The property may be used to indicate that an Appointment occurs on a day or range of days but is not restricted to a particular time within those days. By default, appointments are rendered differently than non-AllDayEvent appointments. The appearance of all AllDayEvent type appointments can be adjusted by changing the . The can be used to change the appearance for all appointments. The appearance of an appointment can also be controlled on an individual basis by adjusting its

A new Appointment, can be created by either creating a new instance of an and adding it to the collection or using the method of the collection. An appointment can also be created using the . To display the AppointmentDialog for a new appointment, use the . The overload may be used to display the appointment information for an existing Appointment.

An Appointment can have a and associated with it. When the is reached, the will be displayed and the will be invoked as long as each is enabled.

Resets the properties of the associated with the .

Use this method to determine if an Appearance object has been created and contains data that needs to be serialized.

Use this method to reset the property. If the property was set to an Appearance from the collection, the properties on the object in the collection will remain the same but the property will no longer be attached to that . To reset the properties of the associated Appearance object, the method of the Appearance object itself should be invoked instead.

Resets the value of the property.

Resets the value of the property.

Resets the value of the property.

Resets the value of the property.

Resets the value of the property.

Resets the value of the property.

Resets the properties of the associated with the .

Resets the value of the property.

Resets the value of the property.

Resets the value of the property.

The following code will increase an appointment by one hour.

[VB]

UltraCalendarInfo1.Appointments(0).OffsetStartTime(System.TimeSpan.FromHours(1))

[C#]

ultraCalendarInfo1.Appointments[0].OffsetStartTime(System.TimeSpan.FromHours(1));

This method is helpful since, with the introduction of recurring appointments, it is possible to have multiple instances of an appointment object generated for the same instance/date of the recurrence. This is a consequence of our design decision to not internally cache references to the generated recurrence appointment objects. If we had cached those references then the objects, once generated would never be garbage collected until the component was.

The AppointmentAction object contains information regarding the type of action to perform as well as the command and parameters to pass to the action.

If the AppointmentAction object is enabled, the action will be invoked when the start date and time of the owning Appointment object has occurred.

The Appearance property of an object is used to associate the object with an Appearance object that will determine its appearance. The Appearance object has properties that control settings such as color, borders, font, transparency, etc. For many of the objects in the UltraSchedule, you do not set formatting properties directly. Instead, you set the properties of an Appearance object, which controls the formatting of the object it is attached to.

There are two ways of working with the Appearance property and assigning the attributes of an SSAppearance object to other objects. One way is to create a new Appearance object, adding it directly to the Appearances collection. Then you assign the new Appearance object to the Appearance property of the object you want to format. This method uses a "named" Appearance object that you must explicitly create (and to which you must assign property settings) before it can be used. For instance, you could create an object in the component's Appearances collection and assign it some values as follows:

UltraMonthViewSingle1.Appearances.Add "New1"

UltraMonthViewSingle1.Appearances("New1").BorderColor = Color.Blue

UltraMonthViewSingle1.Appearances("New1").ForeColor = Color.Red

Creating the object in this way does not apply formatting to any visible part of the control. The object simply exists in the collection with its property values, waiting to be used. To actually use the object, you must assign it to the control's (or another object's) Appearance property:

UltraMonthViewSingle1.Appearance = UltraMonthViewSingle1.Appearances("New1")

In this case, only one Appearance object exists. The control's appearance is governed by the settings of the "New1" object in the collection. Any changes you make to the object in the collection will immediately be reflected in the control.

The second way of working with the Appearance property is to use it to set property values directly, such as:

UltraMonthViewSingle1.Appearance.ForeColor = Color.Blue

In this case, an Appearance object is automatically created by the control. This Appearance object is not a member of an Appearances collection and it does not have a name. It is specific to the object for which it was created; it is an "intrinsic" Appearance object. Changes to the properties of an intrinsic Appearance object are reflected only in the object to which it is attached.

Note that you can assign properties from a named Appearance object to an intrinsic Appearance object without creating a dependency relationship. For example, the following code...

UltraMonthViewSingle1.Appearance.ForeColor = UltraMonthViewSingle1.Appearances("New1").ForeColor

...does not establish a relationship between the foreground color of the intrinsic object and that of the named object. It is simply a one-time assignment of the named object's value to that of the intrinsic object. In this case, two Appearance objects exist - one in the collection and one attached to the control - and they operate independently of one another.

If you wish to assign all the properties of a named object to an intrinsic object at once without creating a dependency relationship, you can use the Clone method of the Appearance object to duplicate its settings and apply them. So if you wanted to apply all the property settings of the named Appearance object "New1" to the control's intrinsic Appearance object, but you did not want changes made to "New1" automatically reflected in the control, you would use the following code:

UltraMonthViewSingle1.Appearance = UltraMonthViewSingle1.Appearances("New1").Clone

Note that the properties of an Appearance object can also operate in a hierarchical fashion. Certain properties can be set to a "use default" value, which indicates to the control that the property should take its setting from the object's parent. This functionality is enabled by default, so that unless you specify otherwise, child objects resemble their parents, and formatting set at higher levels of the control hierarchy is inherited by objects lower in the hierarchy.

Use this property to determine if an object has been created. Appearance objects in general are not created until the properties associated with them are accessed.

All-day events display as a boxed item in the MonthView and WeekView controls and at the top of the DayView control.

The AppointmentAction object contains information regarding the type of action to perform as well as the command and parameters to pass to the action.

Setting the Day of the does not affect the duration of the Appointment. Instead, it offsets the start of the Appointment based on the difference in days between the current and the of the specified Day object. The same behavior can be achieved by using the method.

The CalendarInfo property can be used to move the to a different object's .

Note: Setting the CalendarInfo property to null (Nothing in VB) is not permitted and will cause an exception to be thrown.

Also note that when the CalendarInfo property is set to a different instance, it is removed from the of the original one. If the event is canceled, setting the CalendarInfo property will have no effect.



Similarly, if the event is canceled, setting the CalendarInfo property will have no effect.



If the is when its CalendarInfo property is set, the property is set to false when it is moved to the new instance.

If the is currently open in either the or the , the dialog is closed before the is moved to the new instance.

To select an , add the object to the property of the owning component.

[VB]

Dim appt as Infragistics.Win.UltraWinSchedule.Appointment

appt = Me.UltraCalendarInfo1.Appointments.Add(System.DateTime.Today, "New Appointment")

Me.UltraCalendarInfo1.SelectedAppointments.Add( appt )

[C#]

Infragistics.Win.UltraWinSchedule.Appointment appt = this.ultraCalendarInfo1.Appointments.Add(System.DateTime.Today, "New Appointment");

this.ultraCalendarInfo1.SelectedAppointments.Add( appt );

The IsMultiDay property returns whether the Appointment's and occur on two different dates.

With the NAS2005 Vol 1 addition of the property, an Appointment can span across multiple logical days even when its and occur on the same actual date; in this case, the IsMultiDay property will return true.

Note: When using the or methods to serialize the , the contents of the DataKey property must support serialization, or an exception will be thrown when the appointment is serialized.

Only objects that are the of an will return a non-null value from this property; 'standalone' appointments and variances (members of a recurrence that have been modified) both return null from this property.

Note: Attempting to set the Recurrence property of an Appointment that is a member of an existing object’s collection will result in an exception being thrown. Similarly, assigning an object that is already assigned to some other object’s Recurrence property results in an exception being thrown. Also note that setting the or property of an whose Recurrence property is set will result in an exception being thrown.

Note: For objects that are not members of a recurrence, the value of the property is returned.

The IsRemoved marks a member of a recurrence as having been logically removed.

When the AllDayEvent property returns true, the Start property returns midnight of the day that contains the actual value of the StartDateTime property, i.e., the time component is stripped out.

When the AllDayEvent property returns true, the End property returns a value that is 23 hours, 59 minutes, and 59 seconds later than midnight of the day that contains the value of the EndDateTime property. When AllDayEvent returns false, the End property returns a value that is one second earlier than the actual value of the EndDateTime property.

An AppointmentAction is used to execute an application when the of the associated is reached. The action can also be executed explicitly using the method.

Note: the will not be invoked if the property is set to false. Also, when using the overload, it is up to the application to honor the window style specified.

Normally an AppointmentAction is not created outside of the assembly but instead is created by an Appointment object when it is first requested.

Resets the value of the property.

Resets the value of the property.

Resets the value of the property.

Resets the value of the property.

The Command property, along with the property, is used to start a new process when either the method is called or when the start time of the is reached if the AppointmentAction is enabled. The command may be the file name of an executable or a file name with an extension that has an application association on the target machine.

The Enabled property controls whether the AppointmentAction is invoked when the start time of the associated is reached.

With the NetAdvantage 2009 Volume 1 release, the AppointmentRecurrence was refactored to move most of its functionality to a base class, the DateRecurrence class. This class contains almost all of the properties that were originally exposed by the AppointmentRecurrence class; the only properties that were left on the AppointmentRecurrence class were the ones that were specific to appointments (OccurrenceStartTime, OccurrenceDuration, RootAppointment, and Variances)

The DateRecurrence class is used to define date patterns which are used by the OwnerTimeSlotSettings class.

The GetDateOfNextOccurrence method can be used to obtain the date of the next occurrence on or after a given date.

The RecurrenceDialog class has been modified to provide a front end for editing a DateRecurrence as well as an AppointmentRecurrence. The constructor now exposes an overload which takes a reference to a DateRecurrence instance, and returns the result of the dialog session via its DateRecurrence property.

Note: The first occurrence of the recurrence does not necessarily coincide with the RangeStartDate, but will never occur earlier than this date.

Setting the RangeStartDate property to a value that is outside the range determined by the associated CalendarInfo's and properties will cause an exception to be thrown.

Note: When an object is detached from an to which it was previously assigned, it is disposed of. A consequence of this is that all members of the collection are removed from the associated component's collection.

Note: If the OccurrenceDuration property is set such that it would cause occurrences to overlap, an exception is thrown.

Note: If the PatternDayOfMonth property is set to a value that exceeds the number of days in any of the months that the recurrence spans, the occurrence for those months will fall on the last day of that month.

Note: The value of the PatternDaysOfWeek property is expressed as bitflags, so that multiple days can be represented by the property.

When the property is set to 'Daily', the PatternDaysOfWeek property can only be set to 'All' or 'AllWeekdays'; setting the property to any other value will result in an exception being thrown.

When the property is set to 'Weekly', the PatternDaysOfWeek property cannot be set to 'None'; doing so will result in an exception being thrown.

When the property is set to 'Monthly' or 'Yearly', the PatternDaysOfWeek property is not applicable.

Note: Since certain values are not valid for the property when PatternFrequency is set to 'Daily' or 'Weekly', the value of the property may be changed when PatternFrequency is set to 'Daily' or 'Weekly'.

The PatternInterval property works in conjunction with the property to determine the cycle of the recurrence. For example, if the PatternFrequency is set to 'Daily', and the PatternInterval is set to 2, the recurrence occurs every other day.

Note: The PatternInterval property is not applicable when the property is set to 'Yearly'. Also note that the maximum allowable value for the PatternInterval property is 99.

Note: The PatternMonthOfYear property is only applicable when the property is set to 'Yearly'.

Note: The PatternOccurrenceOfDayInMonth property is only applicable when the property is set to 'Monthly' or 'Yearly'.

Note: The PatternType property is only applicable when the property is set to 'Monthly' or 'Yearly'.

Note: When is set to 'NoLimit' or 'LimitByNumberOfOccurrences', setting the RangeEndDate property has no effect; the return value will be calculated, using the recurrence's pattern criteria, for the number of occurrences specified by the property.

The last occurrence of the recurrence does not necessarily coincide with the RangeEndDate, but will never occur later than this date.

Setting the RangeEndDate property to a value that is outside the range determined by the associated CalendarInfo's and properties will cause an exception to be thrown.

Note: The RangeMaxOccurrences property is applicable only when the property is set to 'LimitByNumberOfOccurrences'. Also note that the maximum allowable value for the RangeMaxOccurrences property is 999.

Note: The first occurrence of the recurrence does not necessarily coincide with the RangeStartDate, but will never occur earlier than this date.

Setting the RangeStartDate property to a value that is outside the range determined by the associated CalendarInfo's and properties will cause an exception to be thrown.

The object referenced by the RootAppointment belongs to the collection. The property of an object that is a root appointment returns an instance of an object whereas all other types of s return null.

Note: Setting the or properties of an object that is assigned to an 's RootAppointment property will cause an exception to be thrown. To modify the starting time of an , set the property. To modify the duration of an , set the property.

Note: The Variances collection's property returns zero if the has not yet been assigned to an .

Returns an object associated with the event. Note, the value may be null.

Note: Because the has already been deleted, its property is no longer valid; the Variance property of the can be used to determine if the appointment was a variance before it was deleted.

Note: Because the has already been deleted, its property is no longer valid; the IsRecurringAppointmentRoot property of the can be used to determine if the appointment was a recurring appointment root before it was deleted.

When the contains invalid values in one or more of its fields, this property can assume a default value of false; for example, if AppointmentRecurrence is set to generate occurrences that would begin or end at a time that is outside the range defined by the associated CalendarInfo's and properties. Listeners can, however, set the SaveChanges property to a different value to override the default behavior.

Modifications that are made to the are not saved until the dialog is closed, and only if the dialog is closed via the 'Ok' button. From this it follows that changes are not applied unless the property is set to true; however, if the dialog remains open after the 'Ok' button is clicked, and SaveChanges is set to true, dialog fields will contain whatever values were entered by the end user, regardless of whether they are valid.

When the contains invalid values in one or more of its fields, this property can assume a default value of false; for example, if AppointmentRecurrence is set to generate occurrences that would begin or end at a time that is outside the range defined by the associated CalendarInfo's and properties. Listeners can, however, set the CloseDialog property to a different value to override the default behavior.

The Message property can contain a value by default in some circumstances; for example, if AppointmentRecurrence is set to generate occurrences that would begin or end at a time that is outside the range defined by the associated CalendarInfo's and properties. Listeners can set the Message property to an empty string to prevent the message from being displayed to the end user.

The Message property can be set to any non-empty string value, which is then displayed in a MessageBox, regardless of whether any of the 's fields contain invalid values.

The AppointmentsCollection contains a reference to all the objects for the object and can be accessed via the property.

The collection can be used to retrieve only the appointments that are currently selected. The appointments associated with a particular time frame may be returned in a object.

When the contents of the has changed, an internal flag is set which indicates that the contents must be sorted the next time the collection is accessed. In the case where a large number of items are being added, or an has changed (or has been assigned to the property), this can affect performance adversely. The SuspendSort method can be used to prevent this automatic sorting for the period of time during which a potentially expensive operation is being performed, so that sorting is suspended until the method is called.

Note: The method must be called after the SuspendSort method is used so that the contents of the collection are sorted before the collection is accessed; failure to do so can result in unpredictable behavior since the ordinal positions of the objects in the collection will not coincide with their chronological order, which is necessary for the component's correct functionality.

Note: The ResumeSort method must be called after the method is used so that the contents of the collection are sorted before the collection is accessed; failure to do so can result in unpredictable behavior since the ordinal positions of the objects in the collection will not coincide with their chronological order, which is necessary for the component's correct functionality.

Note: A parameterless constructor is required for all derived classes.

Since this event is being fired before the selection change has actually taken place, the contents of the collection returned by this property may be compared against the property to see the changes that have occurred.

Since this event is being fired before the selection change has actually taken place, the contents of the collection returned by this property may be compared against the property to see the changes that have occurred.

Since this event is being fired before the selection change has actually taken place, the contents of the collection returned by this property may be compared against the property to see the changes that have occurred.

Returns a object associated with the event. Note, the value may be null.

Returns a object associated with the event. Note, the value may be null.

Returns a object associated with the event.

Returns a object associated with the event.

Since this event is being fired before the selection change has actually taken place, the contents of the collection returned by this property may be compared to the property to see the changes that have occurred.

If the property is true and the DisplayMaxSelectedDaysErrorMsg is true, a dialog will be displayed to the end user after the event fires. Setting this property to false will prevent the dialog from being displayed.

The dialog will only be displayed if MaxSelectedDays was exceeded.

If the IsExistingAppointment returns false, the Appointment referenced by the is a new object.

Note: This property is only applicable when the is a member of a recurrence, or is itself a recurring appointment root.

When the contains invalid values in one or more of its fields, this property can assume a default value of false; for example, if an appointment's or property is outside the range defined by the associated CalendarInfo's and properties. Listeners can, however, set the SaveChanges property to a different value to override the default behavior.

When the contains invalid values in one or more of its fields, this property can assume a default value of false; for example, if an appointment's or property is outside the range defined by the associated CalendarInfo's and properties. Listeners can, however, set the CloseDialog property to a different value to override the default behavior.

The Message property can contain a value by default in some circumstances; for example, if an appointment's or property is outside the range defined by the associated CalendarInfo's and properties. Listeners can set the Message property to an empty string to prevent the message from being displayed to the end user.

The Message property can be set to any non-empty string value, which is then displayed in a MessageBox, regardless of whether any of the 's fields contain invalid values.

Note: The Message property is not applicable if the property is set to false.

The UltraDayView, UltraWeekView, and UltraMonthViewSingle classes derive from this base class.

By default, the ControlWithActivityBase-derived controls use the EditorWithText embeddable editor to edit appointments. The AppointmentEditorComponent property can be used to assign a different embeddable editor to be used for editing appointments.

The AppointmentEditor property is available only at runtime.

By default, the ControlWithActivityBase-derived controls use the EditorWithText embeddable editor to edit appointments. The AppointmentEditorComponent property can be used to assign a different embeddable editor to be used for editing appointments.

The AppointmentEditorComponent property cannot be set to a component that does not implement the IProvidesEmbeddableEditor interface; doing so will cause an exception to be thrown.

The AppointmentsDragging event notifies a listener during all phases of an appointment drag operation. The Phase property identifies whether the drag operation has just been initiated, is continuing because the end user is moving the mouse while the logical left button is pressed, or is about to be committed because the end user released the mouse. The event can be canceled during any phase, in which case the dragged appointment(s) are returned to their pre-drag state. A listener can use this event for the following purposes:

• Prevent the appointment(s) from being dragged to a different Owner (see AllowOwnerChange)
• Prevent copies of the the appointment(s) from being made during the drag operation (see AllowCopy)
• Initiate an external drag/drop operation (for example, drag appointments to a different control) by canceling the event for the 'Beginning' phase and calling the control's DoDragDrop method
• Specify the cursor to be displayed during the drag operation (see MoveCursor, CopyCursor)
• Trigger a standard .NET drag/drop operation to (for example) a different control.

If this event is not canceled, the AppointmentsDragDrop event is fired at the end of the drag operation.

Appointments can be dragged to another control by canceling the AppointmentsDragging event, and calling the DoDragDrop method on the schedule control from which the appointments are being dragged. Note that the drop target control must in this case have its AllowDrop property set to true, and the developer must also handle its DragDrop event in order to process the data.

The AppointmentsResizing event notifies a listener during all phases of an appointment resize operation. The Phase property identifies whether the resize operation has just been initiated, is continuing because the end user is moving the mouse while the logical left button is pressed, or is about to be committed because the end user released the mouse. The event can be canceled during any phase, in which case the resized appointment is returned to its pre-drag state. The SelectionAction property can be used to determine how the existing appointment selection is affected when the resize operation begins, i.e., whether the existing selection is cleared, preserved, or if only the appointment being resized is selected.

If this event is not canceled, the AppointmentResized event is fired at the end of the resize operation.

The AppointmentsDragDrop event notifies a listener than the user has completed a drag operation involving one or more appointments, and that the drag operation was not canceled.

The AppointmentResized event notifies a listener than the user has completed an appointment resizing operation, and that the operation was not canceled. The EnterEditMode property can be used to determine whether the resized appointment automatically enters edit mode when the resize operation has been completed.

When the drag operation is initiated, the NewDateTime and InitialDateTime are the same. As the user moves the cursor over areas of the control which represent a different date, the value of the NewDateTime property changes to reflect the date which is used to determine the new date for the appointments.

During the lifetime of the drag operation, the Appointments property returns the same instances as the appointments contained within the SelectedAppointments collection, excluding any appointments therein whose Locked property is set to true.

Note: It is strongly recommended that the appointments contained within this collection not be removed from their owning Appointments collection during the lifetime of the drag operation. Doing so can result in an exception being thrown or other unpredictable behavior.

A return value of 'Beginning' indicates that this is the first firing of the event for the associated operation; a value of 'Moving' indicates that the operation is currently underway, and the user has moved the cursor to a different day or TimeSlot since the last time the event was fired. A return value of 'CopyStatusChanging' indicates that the user has pressed or released the Control key, changing the copy status of the drag operation.

To support legacy behavior, the AllowOwnerChange property defaults to true.

To support legacy behavior, the AllowCopy property defaults to true.

When the AllowCopy property is explicitly set to false, this property returns false as well.

When the drag operation is initiated, the NewOwner and InitialOwner reference the same object. As the user moves the cursor over areas of the control which represent a different owner, the value of the NewOwner property changes to reflect the owner with which the appointments will be associated if the drag operation is not canceled.

When the MoveCursor property is not explicitly set, the default "drag" cursor is displayed.

When the CopyCursor property is not explicitly set, the default "drag copy" cursor is displayed.

A return value of 'Beginning' indicates that this is the first firing of the event for the associated operation; a value of 'Moving' indicates that the operation is currently underway, and the user has moved the cursor to a different day or TimeSlot since the last time the event was fired.

This property is only applicable when the Phase property returns 'Beginning'. Setting this property during any other phase has no effect.

To support legacy behavior, this property defaults to 'ClearExistingSelection' for the UltraDayView control, and 'PreserveExistingSelection' for the UltraMonthViewSingle and UltraWeekView controls.

The Appointments property returns a read-only collection consisting of the actual appointments that were dragged, with start and end times that reflect the result of the drag operation. The CopiedAppointments property, by contrast, returns clones of the appointments that were dragged. For example, if an appointment is dragged from the current day to the following day, and the control key is pressed before the drag operation is completed, the Appointments property returns the same instance as the appointment that was dragged to the following day, and the CopiedAppointments property returns the one that belongs to the current day. When the drag operation is completed, the SelectedAppointments collection contains the same instances as those returned by the Appointments property.

To support legacy behavior, the SelectedAppointments collection is cleared when the active owner changes. Unless the ClearSelectedAppointments property is explicitly set to false by a listener, the dragged appointments are deselected immediately after this event fires, if the owner on which they are dropped is different than the inital owner.

The CopiedAppointments collection returns a null reference when the HasCopies property returns false, so callers should either check the HasCopies property or check for a null reference before accessing the contents of the CopiedAppointments collection.

When the HasCopies property returns false, this property always returns null.

The CopiedAppointments property returns a read-only collection consisting of clones of the appointments that were dragged, with the same start and end times as the original appointments. The Appointments property, by contrast, returns the actual appointments that were dragged. For example, if an appointment is dragged from the current day to the following day, and the control key is pressed before the drag operation is completed, the Appointments property returns the same instance as the appointment that was dragged to the following day, and the CopiedAppointments property returns the one that belongs to the current day. When the drag operation is completed, the SelectedAppointments collection contains the same instance as the appointment that was dragged to the following day.

To support legacy behavior, the SelectedAppointments collection is cleared when the active owner changes; set the ClearSelectedAppointments property to false to prevent this.

The HasCopies property basically indicates whether the Control key was pressed at the time the event was fired, and the AllowCopy of the event arguments for the AppointmentsDragging event was set to true. If HasCopies returns true, the CopiedAppointments collection returns a non-null value.

The NAS2004 Volume 3 release of UltraWinSchedule includes support for data binding the UltraCalendarInfo component's Notes collection. The Notes collection can be populated from the contents of any IList implementor, for example, a DataTable. To identify the names of the members that contain the property values for each Note object, the and the properties must be set. The contents of the fields that correspond to these members supply the values for the Note object's and properties, respectively. Each item in the list (for example, the individual rows in a DataTable) represents a member of the Notes collection. As property values of the Note object change, the new value is written to the corresponding member of the data source.

Because of a confirmed bug in the class whereby a DateTime's status as either a local or universal time is not preserved during the serialization process, the property cannot always properly honor the 'SerializeDatesAsUniversalTime' setting. Dates that were serialized in the UTC format would appear in the resulting XML as local times, and thus when deserialized would be interpreted as such. Since the WinSchedule data binding layer converts dates that were serialized as universal times into the local time for the current time zone, dates would appear incorrectly, since the method has no effect on a DateTIme whose Kind property returns 'Local'.

If, for example, the DateMemberSerializationMode property is set to 'SerializeDatesAsUniversalTime', and an that occurs at 8AM EST is serialized to an XML file, the WinSchedule data binding layer will convert the date to its UTC equivalent, resulting in a time of 1PM. The resulting string in the XML file, however, appears with the time zone-specific "-05:00" suffix, which causes the DateTime parser to interpret the date as being expressed in local time, which in turn causes the date to incorrectly appear as 1PM EST when it is deserialized from the XML file.

By setting the property to 'IgnoreDateTimeKind', the WinSchedule data binding layer is instructed to remove the DateTimeKind information from the deserialized date, effectively clearing its status as a local time, so that the DateTime's ToLocalTime method performs as expected.

Note that the exists as a convenience to the end developer to provide a solution to the specific problem created by the above mentioned limitation in the SoapFormatter class, and should only be used in scenarios where it is known conclusively that the DateTime data being deserialized contains corretc date and time information, but an incorrect or undefined value for the Kind property.

Use this method to determine if an Appearance object has been created and contains data that needs to be serialized.

Use this method to reset the property. If the property was set to an Appearance from the collection, the properties on the object in the collection will remain the same but the property will no longer be attached to that . To reset the properties of the associated Appearance object, the method of the Appearance object itself should be invoked instead.

Use this method to determine if an Appearance object has been created and contains data that needs to be serialized.

Use this method to reset the property. If the property was set to an Appearance from the collection, the properties on the object in the collection will remain the same but the property will no longer be attached to that . To reset the properties of the associated Appearance object, the method of the Appearance object itself should be invoked instead.

Use this method to determine if an Appearance object has been created and contains data that needs to be serialized.

Use this method to reset the property. If the property was set to an Appearance from the collection, the properties on the object in the collection will remain the same but the property will no longer be attached to that . To reset the properties of the associated Appearance object, the method of the Appearance object itself should be invoked instead.

Note that not all styles are available on all operating systems. If the version of the OS that your program is running on does not support a particular border style, borders formatted with that style will be drawn using solid lines.

When the property is set to Default, the control's default setting, Raised, will be used.

Use this property to determine if an object has been created for the property. Appearance objects in general are not created until the properties associated with them are accessed.

Use this property to determine if an object has been created for the property. Appearance objects in general are not created until the properties associated with them are accessed.

Use this property to determine if an object has been created for the property. Appearance objects in general are not created until the properties associated with them are accessed.

The SpinButtonIncrement determines the units of change applied to the value when a spin button is pressed. The units can be days, weeks, months, and year. The number of these increments that are applied to the value is determined by the .

Note: The Value may still be incremented by the value even when the spin buttons are not visible since by default the up and down arrow keys are interpretted as an increment using the spin buttons when the control is not dropped down.

When clicking the up spin arrow or using the up arrow key, a positive number of the SpinButtonIncrementValues are applied. When clicking the down spin button or using the down arrow key when the control is not dropped down will apply a negative amount of those units.

The BeforeDropDown event can be canceled; when this happens, the dropdown list is not displayed, and the event does not fire.

The TimeRange class encapsulates a range of time through two simple properties, StartTime and EndTime, both of which are of type TimeSpan. This class makes it possible to define a range of time as a working hour range, or specify an appearance that applies to a given range of time.

The TimeSlot class enacapsulates a range of time as it pertains to the UltraDayView control, with the number of time slots displayed by the control being dependent on the value of the TimeSlotInterval property. The main purpose of the TimeRange class is to simplify syntax when defining a range of working hours or applying an appearance to time slots; rather than creating an object for each TimeSlot to be affected, a TimeRange object can be used to represent multiple TimeSlots with a single object.

The IsInRange method can be used to determine whether a TimeSlot falls within the range defined by this instance.

The value of the parameter is treated as an exclusive value when a TimeSlot is compared to this instance to determine whether it is within range. For example, if a TimeRange instance is created with a StartTime of 09:00, and an EndTime of 12:00, a TimeSlot whose StartTime is exactly equal to 12:00 is considered to be outside the range defined by that instance.

Because the value of the EndTime property is treated as an exclusive value, a TimeSlot whose StartTime time component is exactly equal to the value of the EndTime property of this instance is considered to be outside the range defined by this instance.

When formatting the start and end times for display, the current culture's LongTimePattern is used to derive the pattern; the "s" components are then removed to eliminate the seconds component from the displayed string.

Given two different TimeRange instances, one named "a" and the other named "b", each with the same values for their StartTime and EndTime properties, the expression, "a == b" will evaluate to false, i.e., the TimeRange object maintains reference identity. The IsSameAs method makes it possible to determine whether two different TimeRange instances are logically the same.

The end time of a TimeSlot object returns a value that is one minute earlier than the start time of the next TimeSlot. This is to avoid intersection between adjacent TimeSlots. The provides an easy way to create a TimeRange instance that can be used in a WorkingHours or TimeRangeAppearances collection.

The value of the EndTime property is considered to be exclusive, meaning that the time range does not include that actual value, but rather all points in time from the StartTime through the minute preceding the actual value of the EndTime property. For example, if the Start property is set to 09:00 hours, and the End property is set to 17:00 hours, the resulting time range as it applies to working hours or time range appearances would be from 9AM through 4:59:59 PM, i.e., up to but not including 5PM. This is in keeping with the time range model used by the UltraDayView control, where the end time for each TimeSlot coincides with the minute preceding the next slot in chronological order. This method is also employed to simplify coding when programmatically adding members to a TimeRangesCollection.

The OwnerTimeSlotSettings class is the base class from which the OwnerDateSettings, DayOfWeekSettings, and OwnerRecurringDateSettings classes derive. Through the functionality inherited from this base class, each of these classes provide the ability to:

• Designate a date, day of the week, or set of dates (as defined by a recurring pattern) as a "workday"
• Designate multiple, arbitrary ranges of time as "working hours"
• Assign an appearance, to be applied to any arbitrary range of time

The IsWorkDay property can be set explicitly to false to override any previously defined working hours, or explicitly set to true to override more general settings such as the value of a DayOfWeek object's IsWorkDay property. When left at its default value, the next object in the property resolution hierarchy is evaluated.

The WorkingHours collection provides a repository for TimeRange objects. The collection provides a way to define any number of contiguous or discontiguous ranges of time to be considered as working hours for the date or day of the week to which they belong. This provides an extension of the functionality provided by the existing WorkDayStartTime and WorkDayEndTime properties of the DayOfWeek object; where those properties only provide the ability to define one single, contiguous range of time as the working hours for the day, the WorkingHours collection allows a way to define "breaks" in the working day.

The TimeRangeAppearances collection provides a repository for TimeRangeAppearance objects. The collection provides a way to define an appearance for a given range of time, using the same syntax as that used to add members to the WorkingHours collection.

When the IsWorkDay property is explicitly set to a value other than 'Default', that setting takes precedence over the value of the DayOfWeek object's IsWorkDay property.

When the IsWorkDay property is explicitly set to false, the contents of the WorkingHours collection is not applicable, i.e., the entire day is considered to consist of non-working hours.

Since the IsWorkday property is exposed by several different classes, it is possible to define workdays at various different levels, i.e., for a specific date, a day of the week, or based on a recurring date pattern. The following table details order of precedence in the property resolution process for the IsWorkDay property:

Order of precedence	Resolved value
1) OwnerDateSettings	If the Owner's DateSettings collection contains an entry for the date to be resolved, that entry is evaluated. If it does not, the resolution process proceeds to the next level. If IsWorkDay is explicitly set, that value takes precedence over all other levels of the property resolution hierarchy. A TimeSlot displayed for the corresponding date will exhibit the non-working hour appearance if the property is set to false, or the working hour appearance if the property is set to true and the TimeSlot is determined to fall within working hours.
2) OwnerRecurringDateSettings	If the Owner's RecurringDateSettings collection contains one or more members, each one is examined to determine whether the date to be resolved coincides with the recurrence pattern defined by the Recurrence property. If it does not, the resolution process proceeds to the next level. If IsWorkDay is explicitly set, that value takes precedence over the remaining levels of the property resolution hierarchy. A TimeSlot displayed for a date on which there is an occurrence will exhibit the non-working hour appearance if the property is set to false, or the working hour appearance if the property is set to true and the TimeSlot is determined to fall within working hours. Note that in the case where more than one recurrence generates an occurrence for the same date, precedence for that date is given to the instance closest to the beginning of the collection. For this reason it is recommended that when using multiple recurrences to define workdays, the recurrence that generates occurrences at the lowest frequency should be positioned closest to the beginning of the collection. For example, consider two recurrences, one (monthly) that occurs on "the first Monday of each month" whose IsWorkDay property is set to false, and another (daily) that occurs "every weekday" whose IsWorkDay property is set to true. The one that occurs monthly should be inserted at the beginning of the collection, and the daily one after it, otherwise (since the first Monday of the month is also a weekday) the first Monday of the month will resolve through the daily recurrence, and IsWorkDay will resolve to true, where the intent was to resolve it to false.
3) DayOfWeekSettings	The member of the DayOfWeekSettings collection which corresponds to the date to be resolved is referenced; if the IsWorkDay property is explicitly set, that value takes precedence over the remaining levels of the property resolution hierarchy. A TimeSlot displayed for the corresponding day of the week will exhibit the non-working hour appearance if the property is set to false, or the working hour appearance if the property is set to true and the TimeSlot is determined to fall within working hours.
4) DayOfWeek (UltraCalendarInfo)	This is the final level of the property resolution hierarchy. If no other player in the resolution chain had a specific setting, this value makes the final determination. By default, all days except Saturday and Sunday are considered to be workdays. This setting applies to all owners. A TimeSlot displayed for the corresponding day of the week will exhibit the non-working hour appearance if the property is set to false, or the working hour appearance if the property is set to true and the TimeSlot is determined to fall within working hours.

The WorkingHours property makes it possible to designate multiple, discontiguous ranges of time as working hours for a particular date. For example, adding 2 TimeRange instances to the list, one for 9AM to 12PM, and another for 1PM to 5PM, would define the working hours for that date such that 12PM to 1PM would remain in the non-working hour range.

When the WorkingHours collection is non-empty, its contents fully describe the working hours for the associated date/day of the week and Owner, i.e., the WorkingHours collection takes precedence over any other properties that define working hours, namely the WorkDayStartTime and WorkDayEndTime properties of the DayOfWeekSettings and DayOfWeek classes. Furthermore, as soon as one TimeRange is added to the collection, that TimeRange represents the only working hours, and replaces all other criteria. For example, consider a day which was previously considered a workday, with its working hours spanning 8AM to 5PM. If a TimeRange of 9AM to 12PM is added to the WorkingHours collection for the associated day of the week, the working hour range immediately becomes 9AM - 12PM, and no longer includes the hours which were previously considered part of the workday. As soon as working hours are defined in this manner, the developer assumes responsibility for fully defining the working hours.

It should be noted that no Appearance object is specifically defined by this class for working hours or non-working hours. The UltraDayView control and the Owner object both expose such appearances, and those appearances provide the mechanism through which the visual attributes of a TimeSlot can be customized. The WorkingHours property extends more fine-grained control over which hours should be considered "working" hours, thus limiting or expanding the set of time ranges to which these existing appearances are applied. A specific appearance can be applied to any arbitrary range of time, without regard to whether it falls within working hours, using the TimeRangeAppearances collection.

Since the WorkingHours collection is exposed by several different classes, it is possible to define working hours at various different levels, i.e., for a specific date, a day of the week, or based on a recurring date pattern. The following table details order of precedence in the property resolution process for the WorkingHours collection:

Order of precedence	Resolved value
1) OwnerDateSettings	If the Owner's DateSettings collection contains an entry for the date to be resolved, that entry is evaluated. If it does not, the resolution process proceeds to the next level. If explicitly populated, the contents of this collection takes precedence over all other levels of the property resolution hierarchy. If the WorkingHours collection contains one or more TimeRanges, a TimeSlot displayed for the corresponding date will exhibit the working hour appearance if the TimeSlot intersects with any of those TimeRanges, and will exhibit the non-working hour appearance otherwise.
2) OwnerRecurringDateSettings	If the Owner's RecurringDateSettings collection contains one or more members, each is examined to determine whether the date to be resolved coincides with the recurrence pattern defined by the Recurrence property. If it does not, the resolution process proceeds to the next level. If explicitly populated, the contents of this collection takes precedence over remaining levels of the property resolution hierarchy. If the WorkingHours collection contains one or more TimeRanges, a TimeSlot displayed for the corresponding date will exhibit the working hour appearance if the TimeSlot intersects with any of those TimeRanges, and will exhibit the non-working hour appearance otherwise. Note that in the case where more than one recurrence generates an occurrence for the same date, precedence for that date is given to the instance closest to the beginning of the collection. For this reason it is recommended that when using multiple recurrences to define working hours, the recurrence that generates occurrences at the lowest frequency should be positioned closest to the beginning of the collection. For example, consider two recurrences, one (monthly) that occurs on "the first Monday of each month" whose working hours are defined as 10AM - 2PM, and another (daily) that occurs "every weekday" whose working hours are defined as 9AM - 3PM. The one that occurs monthly should be inserted at the beginning of the collection, and the daily one after it, otherwise (since the first Monday of the month is also a weekday) the first Monday of the month will resolve through the daily recurrence, and the working hours will resolve as 9AM - 3PM, where the intent was to resolve them as 10AM - 2PM.
3) DayOfWeekSettings	The member of the DayOfWeekSettings collection which corresponds to the date to be resolved is referenced; if the WorkingHours collection is explicitly populated, its contents take precedence over all other levels of the property resolution hierarchy. A TimeSlot displayed for the corresponding date will exhibit the working hour appearance if the TimeSlot intersects with any of those TimeRanges, and will exhibit the non-working hour appearance otherwise. If the WorkingHours collection is empty, the WorkDayStartTime and WorkDayEndTime properties are evaluated to determine whether they have been explicitly set. If they have, a TimeSlot displayed for the corresponding date will exhibit the working hour appearance if the TimeSlot intersects with the range of time defined by the WorkDayStartTime and WorkDayEndTime properties.
4) DayOfWeek (UltraCalendarInfo)	This is the final level of the property resolution hierarchy. If no other player in the resolution chain had a specific setting, this object makes the final determination. A TimeSlot displayed for this day of the week will exhibit the working hour appearance if the TimeSlot intersects with the range of time defined by the WorkDayStartTime and WorkDayEndTime properties.

Appearance properties are exposed by the UltraDayView control and the Owner class which allow customization of the visual attributes of TimeSlots displayed for working and non-working hours. These appearances, however, apply to all days; the TimeRangeAppearances property provides a mechanism through which these visual attributes can be customized for any arbitrarily selected date and range of time.

A TimeRangeAppearance object overrides all working-hour criteria when a TimeSlot's appearance is resolved.

Since the TimeRangeAppearances collection is exposed by several different classes, it is possible to define appearances at various different levels, i.e., for a specific date, a day of the week, or based on a recurring date pattern. The following table details order of precedence in the property resolution process for the TimeRangeAppearances collection:

Order of precedence	Resolved value
1) OwnerDateSettings	If the Owner's DateSettings collection contains an entry for the date to be resolved, that entry is evaluated. If it does not, the resolution process proceeds to the next level. If the TimeRangeAppearances collection is non-empty, and a member exists whose time range intersects with that of the TimeSlot whose appearance is to be resolved, the TimeSlot resolves its appearance through that member. Note that any properties that are not explicitly set on its appearance are left available to be resolved by the next player in the resolution chain.
2) OwnerRecurringDateSettings	If the Owner's RecurringDateSettings collection contains one or more members, each is examined to determine whether the date to be resolved coincides with the recurrence pattern defined by the Recurrence property. If it does not, the resolution process proceeds to the next level. If the TimeRangeAppearances collection is non-empty, and a member exists whose time range intersects with that of the TimeSlot whose appearance is to be resolved, the TimeSlot resolves its appearance through that member. Note that any properties that are not explicitly set on its appearance are left available to be resolved by the next player in the resolution chain. Note that in the case where more than one recurrence generates an occurrence for the same date, precedence for that date is given to the instance closest to the beginning of the collection. For this reason it is recommended that when using multiple recurrences to define working hours, the recurrence that generates occurrences at the lowest frequency should be positioned closest to the beginning of the collection.
3) DayOfWeekSettings	This is the final level of the property resolution hierarchy. The member of the DayOfWeekSettings collection which corresponds to the date to be resolved is referenced; if the TimeRangeAppearances collection is non-empty, and a member exists whose time range intersects with that of the TimeSlot whose appearance is to be resolved, the TimeSlot resolves its appearance through that member. Note that any properties that are not explicitly set on its appearance are left available to be resolved by the next player in the resolution chain.

The OwnerRecurringDateSettings class makes it possible to specify workdays, working hours, and time range appearances, for a regularly recurring pattern of dates. It uses the same recurrence engine as that which controls Appointment recurrences. The OwnerRecurringDateSettings class inherits a WorkingHours and TimeRangeAppearances collection, as well as an IsWorkDay property, from the OwnerTimeSlotSettings class, and exposes one additional property, Recurrence. The Recurrence property is of type DateRecurrence (from which the AppointmentRecurrence class derives), which provides a general mechanism through which a date pattern can be defined. With this combination of properties, time-slot settings can be controlled for a recurring pattern of dates, allowing the developer to define, for example, working hours for "Monday, Wednesday, and Friday of every other week", "the second Tuesday of November", or "the first weekday of every month".

When a TimeRange is added to this collection, the range is checked against existing instances; if a range is found with which the new range intersects, the two are effectively merged together, resulting in modification of the exsiting instance to include the new range. In this case, the instance passed to the Add method is not added to the collection, and the existing instance is returned.

The contents of this collection are always maintained in chronological order, i.e., when a new instance is added, the collection is sorted by the value of the TimeRange's StartTime property.

If the values of the and parameters define a range of time which intersects with an existing member of this collection, the existing member is modified to incorporate the new range, but no new member is added, and the existing instance is returned.

If the being added defines a range of time which intersects with an existing member of this collection, the existing member is modified to incorporate the new range, but the specified instance is not added.

The members of this collection are stored in a generic dictionary. It supports iteration via a generic IEnumerable implementation for OwnerDateSettings instances, but its members have no notion of an ordinal position within the collection.

Specifying a for which no corresponding member exists will not cause an exception to be thrown. This indexer can also be used to determine whether an instance exists for a given date; when null is returned, no existing instance exists.

The contents of this collection are always maintained in chronological order, i.e., when a new instance is added, the collection is sorted by the value of the associated TimeRange's StartTime property.

Unlike the TimeRangesCollection class, this class supports overlapping time ranges, i.e., instances whose time ranges intersect are allowed to coexist in the collection. In the case where a TimeSlot intersects with more than one of the members of this collection, the one which occurs chronologically earlier takes precedence. For example, if two members are added to this collection, one for 9AM - 10AM and another for 9:30AM to 10:30AM, the 9:30AM TimeSlot will resolve its appearance through the 9AM - 10AM instance first. If, for example, the BackColor property was set on both appearances, the BackColor for the second instance would not be applied, since the first instance had already resolved it.

The Appearance property of an object is used to associate the object with an Appearance object that will determine its appearance. The Appearance object has properties that control settings such as color, borders, font, transparency, etc. For many of the objects in the UltraWinSchedule, you do not set formatting properties directly. Instead, you set the properties of an Appearance object, which controls the formatting of the object it is attached to.

There are two ways of working with the Appearance property and assigning the attributes of an SSAppearance object to other objects. One way is to create a new Appearance object, adding it directly to the Appearances collection. Then you assign the new Appearance object to the Appearance property of the object you want to format. This method uses a "named" Appearance object that you must explicitly create (and to which you must assign property settings) before it can be used. For instance, you could create an object in the component's Appearances collection and assign it some values as follows:

UltraMonthViewSingle1.Appearances.Add "New1"

UltraMonthViewSingle1.Appearances("New1").BorderColor = Color.Blue

UltraMonthViewSingle1.Appearances("New1").ForeColor = Color.Red

Creating the object in this way does not apply formatting to any visible part of the control. The object simply exists in the collection with its property values, waiting to be used. To actually use the object, you must assign it to the control's (or another object's) Appearance property:

UltraMonthViewSingle1.Appearance = UltraMonthViewSingle1.Appearances("New1")

In this case, only one Appearance object exists. The control's appearance is governed by the settings of the "New1" object in the collection. Any changes you make to the object in the collection will immediately be reflected in the control.

The second way of working with the Appearance property is to use it to set property values directly, such as:

UltraMonthViewSingle1.Appearance.ForeColor = Color.Blue

In this case, an Appearance object is automatically created by the control. This Appearance object is not a member of an Appearances collection and it does not have a name. It is specific to the object for which it was created; it is an "intrinsic" Appearance object. Changes to the properties of an intrinsic Appearance object are reflected only in the object to which it is attached.

Note that you can assign properties from a named Appearance object to an intrinsic Appearance object without creating a dependency relationship. For example, the following code...

UltraMonthViewSingle1.Appearance.ForeColor = UltraMonthViewSingle1.Appearances("New1").ForeColor

...does not establish a relationship between the foreground color of the intrinsic object and that of the named object. It is simply a one-time assignment of the named object's value to that of the intrinsic object. In this case, two Appearance objects exist - one in the collection and one attached to the control - and they operate independently of one another.

If you wish to assign all the properties of a named object to an intrinsic object at once without creating a dependency relationship, you can use the Clone method of the Appearance object to duplicate its settings and apply them. So if you wanted to apply all the property settings of the named Appearance object "New1" to the control's intrinsic Appearance object, but you did not want changes made to "New1" automatically reflected in the control, you would use the following code:

UltraMonthViewSingle1.Appearance = UltraMonthViewSingle1.Appearances("New1").Clone

Note that the properties of an Appearance object can also operate in a hierarchical fashion. Certain properties can be set to a "use default" value, which indicates to the control that the property should take its setting from the object's parent. This functionality is enabled by default, so that unless you specify otherwise, child objects resemble their parents, and formatting set at higher levels of the control hierarchy is inherited by objects lower in the hierarchy.

Note: When the and properties are set to non-default values, the end developer is permitted to set the WorkDayStartTime property to a value that occurs later than that of the property. This is so that a logical work day can be specified which spans across more than one day. For example, if the LogicalDayOffset property is set such that the logical day begins at 8PM on the previous day, setting the WorkDayStartTime property to 10PM and the property to 4AM will result in a logical work day which begins at 10PM on the previous day and ends at 4AM on the current day.



Also note that setting the value of the WorkDayStartTime property to a value that is outside the range defined by the logical day properties will result in the value being forced to coincide with the beginning of the logical day.

Note: When the and properties are set to non-default values, the end developer is permitted to set the WorkDayEndTime property to a value that is earlier than that of the property. This is so that a logical work day can be specified which spans across more than one day. For example, if the LogicalDayOffset property is set such that the logical day begins at 8PM on the previous day, setting the property to 10PM and the WorkDayEndTime property to 4AM will result in a logical work day which begins at 10PM on the previous day and ends at 4AM on the current day.



Also note that setting the value of the WorkDayEndTime property to a value that is outside the range defined by the logical day properties will result in the value being forced to coincide with the end of the logical day.

The component extends the ability to specify whether a particular day of the week is a working day, as well as when the working day begins and ends. This functionality is realized though the object; the collection returns one of these objects for each day of the week. The DayOfWeekSettings object extends the ability to specify whether a particular day of the week is a working day, as well as when the working day begins and ends, for the to which the instance is associated. When a property of the DayOfWeekSettings object is set, that value is used for that day of the week; in the absence of a specific setting on the DayOfWeekSettings object, the value from the object (in the UltraCalendarInfo's collection) for that particular day of the week is used.

A DayOfWeekSettings object for each of the seven days of the week can be obtained from the object's collection.

When the and properties are set to non-default values, the end developer is permitted to set the WorkDayStartTime property to a value that occurs later than that of the property. This is so that a logical work day can be specified which spans across more than one day. For example, if the LogicalDayOffset property is set such that the logical day begins at 8PM on the previous day, setting the WorkDayStartTime property to 10PM and the property to 4AM will result in a logical work day which begins at 10PM on the previous day and ends at 4AM on the current day.



Also note that setting the value of the WorkDayStartTime property to a value that is outside the range defined by the logical day properties will result in the value being forced to coincide with the beginning of the logical day.

Note: The date components of the WorkDayStartTime property are not applicable, as the property defines a time of day that is independent of any particular date.

The WorkDayStartTime and WorkDayEndTime properties, while not obsolete, have been enhanced by the addition of the WorkingHours collection property, which makes it possible to define multiple, discontiguous ranges of time as working hours. When the WorkingHours collection is populated, the WorkDayStartTime and WorkDayEndTime properties are not applicable.

Note: For a detailed explanation of the order of precedence used when resolving working hours and time slot appearances, refer to the IsWorkDay, WorkingHours, and TimeRangeAppearances properties of the OwnerTimeSlotSettings class.

When the and properties are set to non-default values, the end developer is permitted to set the WorkDayEndTime property to a value that is earlier than that of the property. This is so that a logical work day can be specified which spans across more than one day. For example, if the LogicalDayOffset property is set such that the logical day begins at 8PM on the previous day, setting the property to 10PM and the WorkDayEndTime property to 4AM will result in a logical work day which begins at 10PM on the previous day and ends at 4AM on the current day.



Also note that setting the value of the WorkDayEndTime property to a value that is outside the range defined by the logical day properties will result in the value being forced to coincide with the end of the logical day.

Note: The date components of the WorkDayEndTime property are not applicable, as the property defines a time of day that is independent of any particular date.

The WorkDayEndTime and WorkDayStartTime properties, while not obsolete, have been enhanced by the addition of the WorkingHours collection property, which makes it possible to define multiple, discontiguous ranges of time as working hours. When the WorkingHours collection is populated, the WorkDayStartTime and WorkDayEndTime properties are not applicable.

Note: For a detailed explanation of the order of precedence used when resolving working hours and time slot appearances, refer to the IsWorkDay, WorkingHours, and TimeRangeAppearances properties of the OwnerTimeSlotSettings class.

The Appearance property of an object is used to associate the object with an Appearance object that will determine its appearance. The Appearance object has properties that control settings such as color, borders, font, transparency, etc. For many of the objects in the UltraWinSchedule, you do not set formatting properties directly. Instead, you set the properties of an Appearance object, which controls the formatting of the object it is attached to.

There are two ways of working with the Appearance property and assigning the attributes of an SSAppearance object to other objects. One way is to create a new Appearance object, adding it directly to the Appearances collection. Then you assign the new Appearance object to the Appearance property of the object you want to format. This method uses a "named" Appearance object that you must explicitly create (and to which you must assign property settings) before it can be used. For instance, you could create an object in the component's Appearances collection and assign it some values as follows:

UltraMonthViewSingle1.Appearances.Add "New1"

UltraMonthViewSingle1.Appearances("New1").BorderColor = Color.Blue

UltraMonthViewSingle1.Appearances("New1").ForeColor = Color.Red

Creating the object in this way does not apply formatting to any visible part of the control. The object simply exists in the collection with its property values, waiting to be used. To actually use the object, you must assign it to the control's (or another object's) Appearance property:

UltraMonthViewSingle1.Appearance = UltraMonthViewSingle1.Appearances("New1")

In this case, only one Appearance object exists. The control's appearance is governed by the settings of the "New1" object in the collection. Any changes you make to the object in the collection will immediately be reflected in the control.

The second way of working with the Appearance property is to use it to set property values directly, such as:

UltraMonthViewSingle1.Appearance.ForeColor = Color.Blue

In this case, an Appearance object is automatically created by the control. This Appearance object is not a member of an Appearances collection and it does not have a name. It is specific to the object for which it was created; it is an "intrinsic" Appearance object. Changes to the properties of an intrinsic Appearance object are reflected only in the object to which it is attached.

Note that you can assign properties from a named Appearance object to an intrinsic Appearance object without creating a dependency relationship. For example, the following code...

UltraMonthViewSingle1.Appearance.ForeColor = UltraMonthViewSingle1.Appearances("New1").ForeColor

...does not establish a relationship between the foreground color of the intrinsic object and that of the named object. It is simply a one-time assignment of the named object's value to that of the intrinsic object. In this case, two Appearance objects exist - one in the collection and one attached to the control - and they operate independently of one another.

If you wish to assign all the properties of a named object to an intrinsic object at once without creating a dependency relationship, you can use the Clone method of the Appearance object to duplicate its settings and apply them. So if you wanted to apply all the property settings of the named Appearance object "New1" to the control's intrinsic Appearance object, but you did not want changes made to "New1" automatically reflected in the control, you would use the following code:

UltraMonthViewSingle1.Appearance = UltraMonthViewSingle1.Appearances("New1").Clone

Note that the properties of an Appearance object can also operate in a hierarchical fashion. Certain properties can be set to a "use default" value, which indicates to the control that the property should take its setting from the object's parent. This functionality is enabled by default, so that unless you specify otherwise, child objects resemble their parents, and formatting set at higher levels of the control hierarchy is inherited by objects lower in the hierarchy.

Do NOT call the Dispose method on the graphics object returned from this method.

Instead, each call to this method should be paired with a call to .

During graphics caching calls to will return a single cached graphics object and calls to will be ignored.

Do NOT call the Dispose method on the graphics object returned from . Use this method instead.

During graphics caching calls to will return a single cached graphics object and calls to will be ignored.

The notes included will be limited to that of the most specific date related trifold section. For example, if a daily section and a monthly section is included, only the notes for the day that is rendered on the page are included in the CalendarInfoNotesArea section.

Note: The RecurrenceDialog was originally designed to provide a front end through which properties of an AppointmentRecurrence instance could be modified. It has been modified to also support editing of a DateRecurrence instance.

This property is only valid when the dialog was created with an AppointmentRecurrence instance, i.e., not when created with a DateRecurrence instance. When the dialog was created with a DateRecurrence instance, this property always returns null.

Note: This property is only valid when the dialog has been closed and the dialog session was not canceled.

When this dialog was created with an AppointmentRecurrence instance, this property returns a downcasted reference, i.e., only properties exposed by the base DateRecurrence class are available. Use the AppointmentRecurrence property when this dialog is used to edit an appointment recurrence.

Note: The RecurrenceEditTypeDialog is displayed for members of a recurrence when the property is set to 'UserSelect' when the event returns, provided that the event has not been canceled.

If is NoGrouping then true is returned.

Otherwise, either the date or owner is compared.

The UltraTimelineView control derives from ControlWithActivityBase and supports the display of appointments and holidays along a horizontal timeline. Display of multiple owners is also supported, with each Owner presented much like a row in a grid. Each division of time is presented much like a column in a grid; each column represents a unit of time whose duration is defined by the PrimaryInterval. Any number of additional date or time intervals can be displayed above the primary interval by adding members to the AdditionalIntervals collection. This collection provides the ability to group the primary intervals, and also to navigate along the timeline by clicking scroll buttons. The number of owners that can be displayed in the viewable area of the control can be changed via the MaximumOwnersInView property, and whether the user can change this value can be controlled via the OwnerSizing property. The number of columns that can be displayed in the viewable area of the control can be changed via the ColumnWidth property, and whether the user can change this value can be controlled via the ColumnSizing property. Text on the headers which represent owners and date/time intervals can be displayed at any orientation using the DateTimeInterval's HeaderTextOrientation property and the control's OwnerHeaderTextOrientation property. Whether appointments are displayed is controlled by the AppointmentVisibility property, and whether holidays are displayed is controlled by the HolidayVisibility property. Whether tooltips are displayed for appointments and holidays can be controlled via the AppointmentToolTipVisibility and HolidayToolTipVisibility properties; tooltips can contain bolded titles, images, and even formatted text, as they are displayed using the Infragistics UltraToolTipManager component. Keyboard behavior is fully customizable via the familiar Infragistics KeyActionMappings paradigm. Events which notify of something that is "about to happen" are cancelable; the firing of any event exposed by the control can be suppressed using the control's EventManager.