SeedCodeComplete2

Event Duration

SeedCodeComplete2.EventDuration History

Hide minor edits - Show changes to output

July 22, 2010, at 04:13 AM by 76.22.123.157 -
Changed lines 38-39 from:
Absolutely. You’ll do this by editing the field definitions of the Events table, changing the definition of the TimeEnd field.
to:
Absolutely. You’ll do this by editing the field definitions of the Events table in the SeedCodeData file, changing the definition of the TimeEnd field.
Changed line 60 from:
Remember, end times are completely optional in SeedCode Calendar, so you don’t need to enter them if you don’t want to.
to:
Remember, end times are completely optional in the calendar, so you don’t need to enter them if you don’t want to.
March 28, 2010, at 06:34 PM by 76.22.123.157 -
Changed line 44 from:
[code]Let ( [\\
to:
-> Let ( [\\
Changed lines 46-57 from:
t = If ( IsEmpty ( Self ) and not IsEmpty ( TimeStart ) ; TimeStart + d ; Self ) ;
t =
Case (
t = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ;
t > Time ( 24 ; 0 ; 0 ) ; t - Time ( 24 ; 0 ; 0 ) ;
t )
] ;
t
)

// v 5.4 modified for default duration[/code]
to:
t = If ( IsEmpty ( Self ) and not IsEmpty ( TimeStart ) ; TimeStart + d ; Self ) ;\\
t = \\
Case ( \\
t = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; \\
t > Time ( 24 ; 0 ; 0 ) ; t - Time ( 24 ; 0 ; 0 ) ;\\
t )\\
] ;\\
t \\
)\\
\\
// v 5.4 modified for default duration\\
March 28, 2010, at 06:33 PM by 76.22.123.157 -
Changed lines 44-45 from:
[code]Let ( [
d = 1200 ; // Default event duration in seconds
to:
[code]Let ( [\\
d = 1200 ; // Default event duration in seconds\\
March 28, 2010, at 06:33 PM by 76.22.123.157 -
Changed lines 40-45 from:
Let’s say you want each event to default to a duration of 1 hours. To begin, select File / Manage / Database. Select the “Fields” tab of the Define Database panel and select SampleEvents (or your events table) from the pop-up list of possible tables. You can now edit the field definition for the TimeEnd to give it a duration. Double click on that field and select the Auto Enter tab of the Field Options window if that tab is not already selected. You’re going to click on the check box beside “Calculated Value”. Once you do, you’ll be taken to a calculation window where you can type in the following:

TimeStart + ( 60 * 60 )

Remember that FileMaker thinks of time in seconds, so we need to multiple 60 seconds by 60 minutes to get a duration of 1 hour. Close the calculation window by clicking OK and then uncheck the check box beside “Do not replace existing value of field
(if any).” That’s it; now each newly created event will have a duration of 1 hour- though you can change the duration by simply editing the event's end time. Note that with the “Do not replace existing value…” box unchecked, any changes to the event's start time will recalculate the end time again.
to:
Let’s say you want each event to default to a duration of 2o minutes. To begin, select File / Manage / Database. Select the “Fields” tab of the Define Database panel and select SampleEvents (or your events table) from the pop-up list of possible tables. You can now edit the field definition for the TimeEnd to give it a duration. Double click on that field and select the Auto Enter tab of the Field Options window if that tab is not already selected. You’re going to click on the check box beside “Calculated Value”. Once you do, you’ll be taken to a calculation window where you'l already see our calc for managing the event ending at midnight.

Replace the existing calc with this:

[code]Let ( [
d = 1200 ; // Default event duration in seconds
t = If ( IsEmpty ( Self ) and not IsEmpty ( TimeStart ) ; TimeStart + d ; Self ) ;
t =
Case (
t = Time
( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ;
t > Time ( 24 ; 0 ; 0 ) ; t - Time ( 24 ; 0 ; 0 ) ;
t )
] ;
t
)

// v 5.4 modified for default duration[/code]

Remember that FileMaker thinks of
time in seconds, so we need to multiple 20 minutes by 60 seconds to get a duration of 20 minutes (1200 seconds). Close the calculation window by clicking OK. That’s it; now each newly created event will have a duration of 20 minutes- though you can change the duration by simply editing the event's end time.
December 29, 2009, at 06:33 AM by 76.22.123.157 -
Changed lines 40-41 from:
Let’s say you want each event to default to a duration of 1 hours. To begin, select File / Manage / Database. Select the “Fields” tab of the Define Database panel and select Events (or your events table) from the pop-up list of possible tables. You can now edit the field definition for the TimeEnd to give it a duration. Double click on that field and select the Auto Enter tab of the Field Options window if that tab is not already selected. You’re going to click on the check box beside “Calculated Value”. Once you do, you’ll be taken to a calculation window where you can type in the following:
to:
Let’s say you want each event to default to a duration of 1 hours. To begin, select File / Manage / Database. Select the “Fields” tab of the Define Database panel and select SampleEvents (or your events table) from the pop-up list of possible tables. You can now edit the field definition for the TimeEnd to give it a duration. Double click on that field and select the Auto Enter tab of the Field Options window if that tab is not already selected. You’re going to click on the check box beside “Calculated Value”. Once you do, you’ll be taken to a calculation window where you can type in the following:
December 18, 2009, at 06:03 PM by 76.22.123.157 -
Added lines 1-46:
!!Can Appointments Span Multiple Days?

Yes. In fact, overnight appointments (when an appointment begins on one day and ends on the next) really span more than one day and SeedCode is programmed to show such an appointment on both days.

If you’d like to create longer multiple day appointments, simply enter a date the “End Date” field in the Event Detail screen when creating or editing an event. (End dates are visible when you edit appointments but are not shown on the daily view; if you use them a lot you could certainly [[AddingFields | add the field to the daily layout]].)

If you add an end date to your event, the event will display on the calendar for each day from the start date through the end date.

Note: If your multi-day event has a start time and an end time, the calendar will color all the hours in between to indicate the duration of the event on the Scheduling tab (if the appointment has a resource) and on the week views (except for the simple week view). This can be fine for some things, but for a multi-day event like “Business Retreat This Week”, you probably don’t want every hour of the whole week colored in. The best way to do this is to leave the times off of this kind of multi-day event. Then create additional events to indicate the start or end times of the event, one event for the start time, and one for the end time.

Consider this example; you’ll be out of town for 5 days on a business trip. Here are the event records you might create to reflect your trip. In this way, only your flight times will show up in the hours column, leaving the hours of your week free to depict other events during your trip.

Record 1\\
Start Date: April 4th\\
End Date: blank\\
Start Time: 6:37 am\\
End Time : blank\\
Description: Flight 304 Departs LA\\
\\
Record 2\\
Start Date: April 4th\\
End Date: April 9th\\
Start Time: blank\\
End Time : blank\\
Description: Business Trip in Hawaii\\
\\
Record 3\\
Start Date: April 9th\\
End Date: blank\\
Start Time: 2:30 pm\\
End Time : blank\\
Description: Flight 706 Departs Hawaii\\
\\
For information about creating repeating appointments, look [[RepeatingEvents | here]].

!!Can I Enter a Default Duration for Each Event?

Absolutely. You’ll do this by editing the field definitions of the Events table, changing the definition of the TimeEnd field.

Let’s say you want each event to default to a duration of 1 hours. To begin, select File / Manage / Database. Select the “Fields” tab of the Define Database panel and select Events (or your events table) from the pop-up list of possible tables. You can now edit the field definition for the TimeEnd to give it a duration. Double click on that field and select the Auto Enter tab of the Field Options window if that tab is not already selected. You’re going to click on the check box beside “Calculated Value”. Once you do, you’ll be taken to a calculation window where you can type in the following:

TimeStart + ( 60 * 60 )

Remember that FileMaker thinks of time in seconds, so we need to multiple 60 seconds by 60 minutes to get a duration of 1 hour. Close the calculation window by clicking OK and then uncheck the check box beside “Do not replace existing value of field (if any).” That’s it; now each newly created event will have a duration of 1 hour- though you can change the duration by simply editing the event's end time. Note that with the “Do not replace existing value…” box unchecked, any changes to the event's start time will recalculate the end time again.

Remember, end times are completely optional in SeedCode Calendar, so you don’t need to enter them if you don’t want to.
(855) SEEDCODE
[email protected]
Follow us: