Thanks you Stefen.
Actually I could dispense with the startTrace/stopTrace mechanism!
For newcomers, here is how to fully debug mobile applications:
1/ Open three tabs in your browser in this order:
It is advised to bookmark these tabs for repeated use.
Tab1 opens a trace file
where xxxxxxxxxxxxxx is some time stamp. The browser window must then display
Tab2 launches the app: do whatever you need then, it will be recorded in the trace file.
Tab3 closes the trace file. The browser window must then display
2/ Return to Tersus Studio
Open the Debug perspective, eg. through menu
Window > Open Perspective > Other... > Debug > OK
Open the Runtime Trace View tab, eg. through menu
Window > Show View > Other > Tersus/Runtime Trace View > OK
Open the trace file, eg. through the 3rd button (from the left) in the right toolbar of the tab. This is the button depicted above in Stefen's answer.
3/ In the Description column of the tab, a tree of actions is displayed, resuming the complete workfolw of the application.
Open this tree with +/-, and select a specific tree entry to inspect the current model or control involved at the current action.
4/ Remark: if you only wish to debug a specific action, you must resort to the the startTrace/stopTrace mechanism. In this case:
- do not open Tab1
- open Tab2 and run the app to the point where the specific action must begin
- perform the specific action
- a trace file Startup-xxxx-xx-xxxxxx has then be created, with xxxx-xx-xxxxxx some time stamp
- do not open Tab3
- follow steps 2/ and 3/ above.
Hope this helps.
For best results, use the Firefox browser..