The Debugger (Magic xpa 3.x)
Magic xpa has a robust debugger and logging system. This is especially useful as you are learning about Rich Client, because you can analyze exactly what your program is doing, and use breakpoints to stop the program when needed. If you are not yet familiar with the Debugger, you can read about it in Mastering Magic xpa.
When you are using the Debugger with Rich Client, be sure to set the Client Activity property to Yes. Otherwise, you will only see the server activity.
The Debugger can also be run remotely, after your application is deployed. Again, if you haven't used this feature, you can read more about it in Mastering Magic xpa.
Logging a server simply displays the local operations. However, logging a client requires it to transfer its operations to the server to be viewed within the Activity Monitor.
Each client context keeps a log of its own operations in cache memory. The Rich Client module will flush the operations to the server in the following cases:
-
The next Rich Client module interaction with the server.
-
At the end of a handler. For example, at the end of the Record Prefix handler, the Rich Client module will flush the operations to the server.
|
|
Note:
Keep in mind that running the Debugger does cause a performance slowdown. You can turn off the Debugger when you are not using it, by clicking on the Debug Mode entry on the Debug menu or 
|
