Topics   All   Mac OS X (Only)   Windows (Only)   Linux (Only, Not)   iOS (Only, Not)  
Components   Crossplatform Mac & Win   Server (Not)   Client   Old   Guides
New in version: 5.4   6.0   6.1   6.2   6.3   6.4   6.5   7.0   7.1   7.2    Statistic  


Starts logging all plugin calls to a text file.

Component: Plugin
Version: 2.4
Mac OS X: Yes
Windows: Yes
Server: Yes
FileMaker Cloud: Yes

MBS( "Trace" { ; path } )


Parameter Description Example value
path Optional
The native file path to the log file.


Returns "OK" on success.


Starts logging all plugin calls to a text file.
If you pass a path, debug messages are written to the file. Else the plugin writes to debug console. See on Mac or DebugView on Windows.
See also Trace.Off and Trace.ErrorsOnly.

On Windows with a FileMaker Server, you can see debug messages in DebugView if you run DebugView application as admin and enable global Win32 listening.
For FileMaker Server on Mac OS X you can see messages in /Library/FileMaker Server/Logs/stderr file.

This function requires a native path. Use Path.FileMakerPathToNativePath to convert a FileMaker path to a native path if required. If you like to have the user choose the path, you can use FileDialog functions.
For Server be aware that server has limited permissions and may not be able to access all files on a computer.


Log plugin calls to console:

MBS( "Trace" )

Log plugin calls to desktop on Windows:

MBS( "Trace"; "C:\Documents\Christian\Desktop\plugin.txt")

Log plugin calls to temp folder on MAc:

MBS( "Trace"; "/tmp/MBS Plugin Log.txt")

Log to log file on desktop:

Set Variable [$TracePath; Value:MBS( "Path.AddPathComponent"; MBS( "Folders.UserDesktop" ); "trace.txt" )]
Set Variable [$r; Value:MBS("Trace"; $TracePath)]

See also

TouchBar.Visible   -   Trace.AreErrorNotificationsEnabled

Feedback: Report problem or ask question.

MBS Realbasic tutorial videos - Pfarrgemeinde Ministranten Nickenich