SeedCodeComplete2

Speed

SeedCodeComplete2.Speed History

Hide minor edits - Show changes to output

Added lines 44-45:
'''•''' If you're entering a lot of events at the same time, you may not want the calendar to refresh after each event is entered. To achieve this simply close the Event Detail window after you've edited the event: the event will still be committed to FileMaker, but since the calendar hasn't refreshed the event won't show up and you can quickly create the next one. Almost any subsequent action will refresh the calendar (switching days, views, etc) and you can always refresh it manually.
Added lines 40-41:
'''•''' The "simple" views for Day and Week are somewhat faster. Select these on the Settings tab in the calendar sidebar. More here: [[Simple Views]].
Changed lines 14-15 from:
'''•''' Speed up the launch by Editing the "Upon Opening" script and disabling the perform of the subscripts "Splash" and "Refresh All Recent Items".
to:
'''•''' Speed up the launch by Editing the "Upon Opening" script and disabling the perform of the subscripts "Splash" and "Refresh All Recent Items".  If you're not going to be moving the solution around or having users from the EU coming in, you can disable a few routines in the Upon Opening routine to speed things up a little. Disable the steps in Upon Opening that follow these comments:

-> Check FileMaker Version
-> Check Dates
-> Write test -- is file editable?
-> Write test -- is data file present and editable?
-> Write test -- is media file present?

Added lines 14-15:
'''•''' Speed up the launch by Editing the "Upon Opening" script and disabling the perform of the subscripts "Splash" and "Refresh All Recent Items".
July 29, 2010, at 03:47 PM by 76.22.123.157 -
Added lines 12-13:
'''•''' Make sure the fields you're mapping to on the "Source No X" layouts are indexed.
Added lines 31-34:

'''•''' If your server is not on the same physical network as your FileMaker client, there could be an undue amount of latency between them slowing things down. %newwin% [[http://network-tools.com/ | Ping]] your FileMaker Server to check this: the results really depend on what kinds of speed you can tolerate, but we you'll likely be happy with pings under 50-70ms. Anything above that and you may want to start asking some of the FileMaker Server hosting providers for test pings to their servers to see if they'd be faster than what you have.

'''•''' Finally, the calendar works harder when it has more work to do, so filtering or pre-filtering to show only the relevant records can speed things up a lot. More on filtering [[Filters | here]].
February 18, 2010, at 05:01 PM by 137.159.253.133 -
Changed line 18 from:
--> If ( $$sc_Mode = "Month" )\\
to:
--> If [ $$sc_Mode = "Month" ]\\
February 18, 2010, at 05:01 PM by 137.159.253.133 -
Changed lines 26-27 from:
#Nothing found?\\
to:
#Nothing found?
February 18, 2010, at 05:00 PM by 137.159.253.133 -
Changed lines 23-27 from:
Omit Record Constrain Found Set [ ]
\\End If
#
#Nothing found?
to:
Omit Record Constrain Found Set [ ]\\
End If\\
#\\
#Nothing found?\\
February 18, 2010, at 05:00 PM by 137.159.253.133 -
Changed lines 23-24 from:
Omit Record Constrain Found Set [ ] End If
to:
Omit Record Constrain Found Set [ ]
\\End If
February 18, 2010, at 04:59 PM by 137.159.253.133 -
Changed lines 23-24 from:
Omit Record Constrain Found Set [ ]
End If
to:
Omit Record Constrain Found Set [ ] End If
February 18, 2010, at 04:59 PM by 137.159.253.133 -
Changed lines 23-24 from:
Omit Record Constrain Found Set [ ]\\End If\\#\\#Nothing found?
to:
Omit Record Constrain Found Set [ ]
End If
#
#Nothing found?
February 18, 2010, at 04:59 PM by 137.159.253.133 -
Changed lines 23-27 from:
Omit Record Constrain Found Set [ ]
End If
#
#Nothing found?
to:
Omit Record Constrain Found Set [ ]\\End If\\#\\#Nothing found?
February 18, 2010, at 04:59 PM by 137.159.253.133 -
Changed lines 24-27 from:
End If\\
#\\
#Nothing found?\\
to:
End If
#
#Nothing found?
February 18, 2010, at 04:58 PM by 137.159.253.133 -
Changed line 23 from:
Omit Record Constrain Found Set [ ]\\
to:
Omit Record Constrain Found Set [ ]
February 18, 2010, at 04:58 PM by 137.159.253.133 -
February 18, 2010, at 04:58 PM by 137.159.253.133 -
Changed lines 19-27 from:
--> Enter Find Mode [ ]
Go
to Object [ Object Name: "SourceTimeStart" ]
Insert
Calculated Result [ "*" ]
[ Select ]
Omit Record Constrain Found Set [ ]
End If
#
#Nothing found?
to:
Enter Find Mode [ ]\\
Go
to Object [ Object Name: "SourceTimeStart" ]\\
Insert
Calculated Result [ "*" ]\\
[ Select ]\\
Omit Record Constrain Found Set [ ]\\
End If\\
#\\
#Nothing found?\\
February 18, 2010, at 04:57 PM by 137.159.253.133 -
Changed line 18 from:
--> If ( $$sc_Mode = "Month" )\
to:
--> If ( $$sc_Mode = "Month" )\\
February 18, 2010, at 04:57 PM by 137.159.253.133 -
Changed lines 10-28 from:
'''•''' Mapping the event summary to a [[MultiLineEvents | multi-line calc]] can slow things down a bit, especially if the calc is unstored. Try using a regular text field (without carriage returns) for your summary instead.
to:
'''•''' Mapping the event summary to a [[MultiLineEvents | multi-line calc]] can slow things down a bit, especially if the calc is unstored. Try using a regular text field (without carriage returns) for your summary instead.

'''•''' You may want to show only All Day events on the month view (since that view has the potential to show the most records, it is potentially the slowest as well). You can restrict the month view in this way pretty easily:

-> Edit the script "Write FileMaker Source to Variable" and find the comment "Nothing Found?".

-> Right *before* that comment add the following:

--> If ( $$sc_Mode = "Month" )\
--> Enter Find Mode [ ]
Go to Object [ Object Name: "SourceTimeStart" ]
Insert Calculated Result [ "*" ]
[ Select ]
Omit Record Constrain Found Set [ ]
End If
#
#Nothing found?

-> That will leave only the all day events
.
February 03, 2010, at 05:08 AM by 76.22.123.157 -
Changed line 10 from:
'''•''' Mapping the event summary to a [[MultiLineEvents | multi-line calc]] can slow things down, especially if the calc is unstored. Try using a regular text field (without carriage returns) for your summary instead.
to:
'''•''' Mapping the event summary to a [[MultiLineEvents | multi-line calc]] can slow things down a bit, especially if the calc is unstored. Try using a regular text field (without carriage returns) for your summary instead.
January 27, 2010, at 02:34 AM by 76.22.123.157 -
Changed lines 8-10 from:
'''•''' If you're not [[AddingFields | showing related fields on the day view]], turn off the "refresh" at the end of the script "Go to Calendar Tab ( Tab Name )"
to:
'''•''' If you're not [[AddingFields | showing related fields on the day view]], turn off the "refresh" at the end of the script "Go to Calendar Tab ( Tab Name )"

'''•''' Mapping the event summary to a [[MultiLineEvents | multi-line calc]] can slow things down, especially if the calc is unstored. Try using a regular text field (without carriage returns) for your summary instead.
January 03, 2010, at 10:31 PM by 76.22.123.157 -
Added line 8:
'''•''' If you're not [[AddingFields | showing related fields on the day view]], turn off the "refresh" at the end of the script "Go to Calendar Tab ( Tab Name )"
January 03, 2010, at 02:18 AM by 76.22.123.157 -
Changed lines 4-7 from:
* Delete or rename any "Source No X" layouts you're not using. So if you're only using 1 source, delete the layout Source No 2 or edit the name by replacing "No" with "Was" as in "Source WAS 2".

Show only one source at a time; when multiple sources are on screen at the same time the calendar sorts them against each other to see which events come first. This take time.
to:
'''•''' Delete or rename any "Source No X" layouts you're not using. So if you're only using 1 source, delete the layout Source No 2 or edit the name by replacing "No" with "Was" as in "Source WAS 2".

'''•''' Show only one source at a time; when multiple sources are on screen at the same time the calendar sorts them against each other to see which events come first. This take time.
January 03, 2010, at 02:17 AM by 76.22.123.157 -
Changed lines 6-7 from:
* Show only one source at a time; when multiple sources are on screen at the same time the calendar sorts them against each other to see which events come first. This take time.
to:
Show only one source at a time; when multiple sources are on screen at the same time the calendar sorts them against each other to see which events come first. This take time.
January 03, 2010, at 02:17 AM by 76.22.123.157 -
Changed lines 4-6 from:
# Delete or rename any "Source No X" layouts you're not using. So if you're only using 1 source, delete the layout Source No 2 or edit the name by replacing "No" with "Was" as in "Source WAS 2".

Show only one source at a time; when multiple sources are on screen at the same time the calendar sorts them against each other to see which events come first. This take time.
to:
* Delete or rename any "Source No X" layouts you're not using. So if you're only using 1 source, delete the layout Source No 2 or edit the name by replacing "No" with "Was" as in "Source WAS 2".

* Show only one source at a time; when multiple sources are on screen at the same time the calendar sorts them against each other to see which events come first. This take time.
January 03, 2010, at 02:17 AM by 76.22.123.157 -
Added lines 1-6:
!! Here are some tips for getting all the speed you can from the calendar...


# Delete or rename any "Source No X" layouts you're not using. So if you're only using 1 source, delete the layout Source No 2 or edit the name by replacing "No" with "Was" as in "Source WAS 2".

Show only one source at a time; when multiple sources are on screen at the same time the calendar sorts them against each other to see which events come first. This take time.
(855) SEEDCODE
[email protected]
Follow us: