DayBackForFileMaker

Refreshing The Calendar

DayBackForFileMaker.RefreshingTheCalendar History

Hide minor edits - Show changes to output

April 10, 2015, at 05:34 PM by 142.4.217.187 -
Changed line 23 from:
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[https://www.seedcode.com/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[https://www.seedcode.com/calendar-as-dashboard/ | this blog post]]. (Where the scripts in that blog post call the script " �Filter Calendar ( Number )�, switch that to the script "Refresh Webviewer Events". =)
to:
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[https://www.seedcode.com/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[https://www.seedcode.com/calendar-as-dashboard/ | this blog post]]. (Where the scripts in that blog post call the script " �Filter Calendar ( Number )�, switch that to the script "Refresh Calendar". =)
April 07, 2015, at 11:07 PM by 142.4.217.187 -
Changed line 23 from:
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[https://seedcodenext.wordpress.com/2011/02/10/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[https://seedcodenext.wordpress.com/2011/11/04/calendar-as-dashboard/ | this blog post]]. (Where the scripts in that blog post call the script " �Filter Calendar ( Number )�, switch that to the script "Refresh Webviewer Events". =)
to:
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[https://www.seedcode.com/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[https://www.seedcode.com/calendar-as-dashboard/ | this blog post]]. (Where the scripts in that blog post call the script " �Filter Calendar ( Number )�, switch that to the script "Refresh Webviewer Events". =)
Changed line 15 from:
-> If you need to refresh using a FileMaker script, call "Refresh Webviewer Events".
to:
-> If you need to refresh using a FileMaker script, call "Refresh Calendar" from the Housekeeping folder.
Added lines 15-16:
-> If you need to refresh using a FileMaker script, call "Refresh Webviewer Events".
Changed line 23 from:
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[https://seedcodenext.wordpress.com/2011/02/10/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[https://seedcodenext.wordpress.com/2011/11/04/calendar-as-dashboard/ | this blog post]]. (Where the scripts in that blog post call the script " �Filter Calendar ( Number )�, switch that to the script "Set Webviewer". =)
to:
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[https://seedcodenext.wordpress.com/2011/02/10/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[https://seedcodenext.wordpress.com/2011/11/04/calendar-as-dashboard/ | this blog post]]. (Where the scripts in that blog post call the script " �Filter Calendar ( Number )�, switch that to the script "Refresh Webviewer Events". =)
Changed line 7 from:
-> This means, that edits and new event records created by other users won't just show up on your display without any interaction on your part. Normally this isn't a big deal as the calendar requests new events from the server each time you a) navigate from day to day, b) apply advanced filters, or c) switch views (like from month to day view). But if you're just staring at your screen, you may want to manually refresh to make sure you have the latest data from the server.
to:
-> This means that edits and new event records created by other users won't just show up on your display without any interaction on your part. Normally this isn't a big deal as the calendar requests new events from the server each time you a) navigate from day to day, b) apply advanced filters, or c) switch views (like from month to day view). But if you're just staring at your screen, you may want to manually refresh to make sure you have the latest data from the server.
Changed line 17 from:
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.
to:
-> The calendar layout has a [[Script triggers | script trigger]] assigned to it which will refresh the calendar each time you arrive.
Changed lines 15-16 from:
'''Refreshing when arriving at the calendar layout'''
to:
'''Refreshing When Arriving at the Calendar Layout'''
Changed line 19 from:
'''Refreshing on a timer'''
to:
'''Refreshing on a Timer'''
Changed line 21 from:
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[https://seedcodenext.wordpress.com/2011/02/10/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[https://seedcodenext.wordpress.com/2011/11/04/calendar-as-dashboard/ | this blog post]].
to:
-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[https://seedcodenext.wordpress.com/2011/02/10/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[https://seedcodenext.wordpress.com/2011/11/04/calendar-as-dashboard/ | this blog post]]. (Where the scripts in that blog post call the script " �Filter Calendar ( Number )�, switch that to the script "Set Webviewer". =)
Changed lines 3-16 from:
'''Editing Events'''

-> When you click on an event in the calendar, we present the event in an Event Details mini window. When you close that window we try to refresh the calendar if you've modified the record, provided you've clicked the green "check" button at the bottom of the window: if you close the window using the Close Window command or the red close button on the window frame, we simply close the window and don't attempt to refresh the calendar.

-> If you're interested in how this works, we're recording the modification state of the record when the window is opened (and this supports having multiple Event Detail windows open at once
). Then when you click our blue button to close the window we're checking the modification count and refreshing the calendar if the event was modified.

-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" before the comment "Commit Record". (Changes made later in the script may be happening on the wrong record as our Dependency Chain scripts may have moved us to another record.)

'''The refresh button'''

-> You'll see a "refresh" button in the calendar header to the right of the arrows that move to the next day/week/month. This button is there in case you'd like to manually ask the server if there are any new events to display. The calendar caches the events it draws and doesn't continually ask the server for new events: this is one reason the calendar is so much faster than traditional FileMaker calendars.

-> This means, however, that edits and new event records won't just show up on your calendar without any interaction on your part. Normally this isn't a big deal as the calendar requests new events from the server each time you edit a record, filter the calendar, or switch views. But if you're just staring at your screen, you may want to click "refresh"
to make sure you have the latest data from the server.
to:
'''When Editing Events or Navigating'''

-> When you click on an event in DayBack, the event is presented in an Event Details popover. When you close that window DayBack will refresh that event, if you've modified the record, but the calendar won't attempt to search for other events that may have been created by other users.

-> This means, that edits and new event records created by other users won't just show up
on your display without any interaction on your part. Normally this isn't a big deal as the calendar requests new events from the server each time you a) navigate from day to day, b) apply advanced filters, or c) switch views (like from month to day view). But if you're just staring at your screen, you may want to manually refresh to make sure you have the latest data from the server.
Added lines 10-13:

'''Manually Refreshing'''

-> If you right-click anywhere in the calendar's display you'll see an option to "reload"; select that and DayBack will refresh the display AND fetch any events that may have been created by other users.
February 25, 2013, at 02:45 AM by 98.245.113.231 -
Changed lines 13-14 from:
-> You'll see a "refresh" button in the calendar header to the right of the arrows that move to the next dat/week/month. This button is there in case you'd like to manually ask the server if there are any new events to display. The calendar caches the events it draws and doesn't continually ask the server for new events: this is one reason the calendar is so much faster than traditional FileMaker calendars.
to:
-> You'll see a "refresh" button in the calendar header to the right of the arrows that move to the next day/week/month. This button is there in case you'd like to manually ask the server if there are any new events to display. The calendar caches the events it draws and doesn't continually ask the server for new events: this is one reason the calendar is so much faster than traditional FileMaker calendars.
May 22, 2012, at 01:58 PM by 50.132.84.245 -
May 22, 2012, at 01:58 PM by 50.132.84.245 -
Changed lines 21-25 from:
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.
to:
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.

'''Refreshing on a timer'''

-> You may want to set the calendar to refresh every few seconds so you can mount a big version in a public space to coordinate schedules. You can see some examples of this %newwin% [[https://seedcodenext.wordpress.com/2011/02/10/whiteboard-versions-of-the-calendar/ | here]] and learn how to automate that refresh in %newwin% [[https://seedcodenext.wordpress.com/2011/11/04/calendar-as-dashboard/ | this blog post]]
.
May 22, 2012, at 01:54 PM by 50.132.84.245 -
Changed lines 9-10 from:
-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" right before or after the commit step after the comment "Commit Record".
to:
-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" before the comment "Commit Record". (Changes made later in the script may be happening on the wrong record as our Dependency Chain scripts may have moved us to another record.)
Changed lines 21-27 from:
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.

'''Refreshing iCal sources'''

-> If you've set up one of your [[multiple sources | sources]] as an iCal URL you many not want to refresh the URL each time you refresh the calendar (as pulling down the URL contents is the slowest thing the calendar does). So we've created a method by which you can specify how often you'd like that URL refreshed.

-> On the Source No X layout you've mapped to this source (as part of your [[integration]]) you'll see a value for "Refresh Every" on the "Recommended" tab. Edit this value in layout mode to reflect the number of hours you'd like to wait between refreshes of the URL. With this value in place, we'll only include the URL in regular calendar refreshes (such as when switching views or editing an event) every X hours
.
to:
-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.
February 03, 2010, at 10:39 PM by 76.22.123.157 -
Changed lines 5-8 from:
-> When you click on an event in the calendar, we present the event in an Event Details mini window. When you close that window we try to refresh the calendar if you've modified the record, provided you've clicked the green "check" button at the bottom of the window: if you close the window using the Close Window command or the red close button on the window frame, we simply close the window and don't attempt to refresh then calendar.

-> If you're interested in how this works we're recording the modification state of the record when the window is opened (and this supports having multiple Event Detail windows open at once). Then when you click our blue button to close the window we're checking the modification count and refreshing the calendar if the event was modified.
to:
-> When you click on an event in the calendar, we present the event in an Event Details mini window. When you close that window we try to refresh the calendar if you've modified the record, provided you've clicked the green "check" button at the bottom of the window: if you close the window using the Close Window command or the red close button on the window frame, we simply close the window and don't attempt to refresh the calendar.

-> If you're interested in how this works, we're recording the modification state of the record when the window is opened (and this supports having multiple Event Detail windows open at once). Then when you click our blue button to close the window we're checking the modification count and refreshing the calendar if the event was modified.
February 03, 2010, at 04:50 AM by 76.22.123.157 -
Changed lines 23-24 from:
Refreshing iCal sources
to:
'''Refreshing iCal sources'''
February 03, 2010, at 04:49 AM by 76.22.123.157 -
Changed lines 11-15 from:
> > the refresh button

> > refreshing when arriving at the calendar layout

> > refreshing iCal sources
to:
'''The refresh button'''

-
> You'll see a "refresh" button in the calendar header to the right of the arrows that move to the next dat/week/month. This button is there in case you'd like to manually ask the server if there are any new events to display. The calendar caches the events it draws and doesn't continually ask the server for new events: this is one reason the calendar is so much faster than traditional FileMaker calendars.

-> This means, however, that edits and new event records won't just show up on your calendar without any interaction on your part. Normally this isn't a big deal as the calendar requests new events from the server each time you edit a record, filter the calendar, or switch views. But if you're just staring at your screen, you may want to click "refresh" to make sure you have the latest data from the server.

-> Note that while this doesn't sound very "FileMaker like", most complicated screens (and certainly most traditional calendars) don't "refresh" automatically either, since the relationships they use for display are too "deep" to respond to notifications of new or edited records from the server.

'''Refreshing when arriving at the calendar layout'''

-> The calendar layouts have a [[Script triggers | script trigger]] assigned to them which will refresh the calendar each time you arrive at the calendar layout.

Refreshing iCal sources

-> If you've set up one of your [[multiple sources | sources]] as an iCal URL you many not want to refresh the URL each time you refresh the calendar (as pulling down the URL contents is the slowest thing the calendar does). So we've created a method by which you can specify how often you'd like that URL refreshed.

-> On the Source No X layout you've mapped to this source (as part of your [[integration]]) you'll see a value for "Refresh Every" on the "Recommended" tab. Edit this value in layout mode to reflect the number of hours you'd like to wait between refreshes of the URL. With this value in place, we'll only include the URL in regular calendar refreshes (such as when switching views or editing an event) every X hours.
December 29, 2009, at 06:56 AM by 76.22.123.157 -
Changed lines 9-15 from:
-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" right before or after the commit step after the comment "Commit Record".
to:
-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" right before or after the commit step after the comment "Commit Record".

> > the refresh button

> > refreshing when arriving at the calendar layout

> > refreshing iCal sources
December 20, 2009, at 12:14 AM by 76.22.123.157 -
December 20, 2009, at 12:14 AM by 76.22.123.157 -
Changed lines 1-9 from:
vvdaVD
to:
!! When does the calendar refresh?

'''Editing Events'''

-> When you click on an event in the calendar, we present the event in an Event Details mini window. When you close that window we try to refresh the calendar if you've modified the record, provided you've clicked the green "check" button at the bottom of the window: if you close the window using the Close Window command or the red close button on the window frame, we simply close the window and don't attempt to refresh then calendar.

-> If you're interested in how this works we're recording the modification state of the record when the window is opened (and this supports having multiple Event Detail windows open at once). Then when you click our blue button to close the window we're checking the modification count and refreshing the calendar if the event was modified.

-> If you'd like to add some additional behaviors to the process of editing an event, add them to the script "Close Window & Refresh Calendar" right before or after the commit step after the comment "Commit Record".
December 20, 2009, at 12:02 AM by 76.22.123.157 -
Added line 1:
vvdaVD
(855) SEEDCODE
support@seedcode.com
Follow us: