Info |
---|
JavaScript_Debugging.html https://wiki.teamdf.com/wiki/pages/E0j6M3c/JavaScript_Debugging.html |
When using the Extended version of the FRToolBox, you get access to a specially built debugger for your JavaScript code, and Reactor CallBacks. If you are developing on a mac, you can also enable access to the wonderful debugging tools in Safari 4 by running a simple command in terminal FileMaker で JavaScript デバッグするには - otherwise, you can just use the debugger built into the ToolBox.
...
Code Block |
---|
Your mum is angry so you had better wash the floor! |
The 'startDebugging' method
This method is best called at the start of your script. Usually, we would automatically run startDebugging if the user has a Development Advanced licence.
...
Any debug messages sent before startDebugging was called will still be available, and will be drawn to the console when debug.show() is run for the first time. We don't always run startDebugging for performance reasons. Some of the debuggers more advanced features intercept and examine calls to natively implemented methods - this has some overhead, so during normal operation it is recommended that startDebugging is not run.
The 'show' method
When called, this function will show the debugger on the screen - provided debug.startDebugging() has been called prior - otherwise it will do nothing.
Code Block |
---|
debug.show() |
The 'hide' method
When called, this function will hide the debugger on the screen - provided the debugger is showing - otherwise it will do nothing.
Code Block |
---|
debug.hide() |
The 'assert' method
This function will attempt to evaluate any passed text in the global context.
...
Code Block |
---|
debug.assert( 'some javascript code' ); |
The 'inspect' method
This function takes the element passed and opens it in the 'HTML' tab for
...
Code Block |
---|
debug.inspect( MyElement ); |
The 'message' method
This function will attempt to display a message diologue which allows the user
...