GoZync5

Debugging

GoZync5.Debugging History

Hide minor edits - Show changes to output

June 24, 2014, at 03:48 AM by 50.132.85.96 -
Changed line 1 from:
!! Tips for Debugging Your Sync
to:
!! Tips for Using the Script Debugger with GoZync5
June 24, 2014, at 03:47 AM by 50.132.85.96 -
Changed lines 7-10 from:
First, if your files are hosted on FileMaker Server, open them on the device you'll be syncing from (your laptop, iPad, or desktop) and run the script "Toggle Perform Script On Server Off For This Session" in your hosted file. (This is one of the scripts you imported when you [[integration | integrated]] GoZync into your solution.)

Running that script will ensure that Perform Script on Server (PSOS) is "Off" for the current session. With PSOS on some of the essential Zync scripts would run on the server away from your script debugger: scripts like the ones where we build the found set of hosted records to sync. With PSOS off the syncs are slower but you can follow more of them in the script debugger.
to:
-> First, if your files are hosted on FileMaker Server, open them on the device you'll be syncing from (your laptop, iPad, or desktop) and run the script "Toggle Perform Script On Server Off For This Session" in your hosted file. (This is one of the scripts you imported when you [[integration | integrated]] GoZync into your solution.)

-> Running that script will ensure that Perform Script on Server (PSOS) is "Off" for the current session. With PSOS on some of the essential Zync scripts would run on the server away from your script debugger: scripts like the ones where we build the found set of hosted records to sync. With PSOS off the syncs are slower but you can follow more of them in the script debugger.
Changed lines 13-18 from:
Some of the scripts in GoZyncHosted are used to validate our licensing of GoZync: you aren't able to edit these scripts.

Thus, when you're using the script debugger you'll want to "step over" these scripts: stepping into them will cause the debugger to run ahead to the next break point and that makes things really hard to follow.

So, when you're debugging keep an eye out for our "DEBUGGING" comments like these in blue:
to:
-> Some of the scripts in GoZyncHosted are used to validate our licensing of GoZync: you aren't able to edit these scripts.

-> Thus, when you're using the script debugger you'll want to "step over" these scripts: stepping into them will cause the debugger to run ahead to the next break point and that makes things really hard to follow.

-> So, when you're debugging keep an eye out for our "DEBUGGING" comments like these in blue:
Changed line 21 from:
You'll want to "step over" the perform script steps that call locked scripts: stepping over is done using the upper leftmost button in the script debugger.
to:
-> You'll want to "step over" the perform script steps that call locked scripts: stepping over is done using the upper leftmost button in the script debugger.
June 24, 2014, at 03:46 AM by 50.132.85.96 -
Added lines 1-21:
!! Tips for Debugging Your Sync

If you have FileMaker advanced and want to follow along with the sync in your script debugger, these tips will make it a bit easier.

'''Turning PSOS OFF'''

First, if your files are hosted on FileMaker Server, open them on the device you'll be syncing from (your laptop, iPad, or desktop) and run the script "Toggle Perform Script On Server Off For This Session" in your hosted file. (This is one of the scripts you imported when you [[integration | integrated]] GoZync into your solution.)

Running that script will ensure that Perform Script on Server (PSOS) is "Off" for the current session. With PSOS on some of the essential Zync scripts would run on the server away from your script debugger: scripts like the ones where we build the found set of hosted records to sync. With PSOS off the syncs are slower but you can follow more of them in the script debugger.

'''Using the Script Debugger with Locked Scripts'''

Some of the scripts in GoZyncHosted are used to validate our licensing of GoZync: you aren't able to edit these scripts.

Thus, when you're using the script debugger you'll want to "step over" these scripts: stepping into them will cause the debugger to run ahead to the next break point and that makes things really hard to follow.

So, when you're debugging keep an eye out for our "DEBUGGING" comments like these in blue:

%center% %width=500px newwin%  [[http://www.seedcode.com/rootimages/stikipad/gozync5/debuggingsteps.png | http://www.seedcode.com/rootimages/stikipad/gozync5/debuggingsteps.png]]

You'll want to "step over" the perform script steps that call locked scripts: stepping over is done using the upper leftmost button in the script debugger.
(855) SEEDCODE
support@seedcode.com
Follow us: