Trying to trace when events fire

[John Fligg]

I think this would help me (and others) to debug their own applications. I tend to get all sorts of issues which a simple demo cannot demonstrate and every issue needs a demo changed. That wastes a lot of time.

In my particular case most of my problems are caused by not knowing what events are firing in what sequence. If I knew that I could then identify embed points to use.

For example when a browse opens, it would be nice to be able to see exactly what events are firing as clearly some in the Update Form are.

Is there a way to switch on like full debug mode and watch the application run using DebugView? That way I can pick out the section I need to trace and hopefully resolve my problems much better.

Thanks

John

[Bruce]

I'm not sure what you mean by "events".
But yes, you can see the incoming requests in the log, in the browser you can see the incoming requests and the replies.

From the server side, if you turn on NetShowSend=>1 in the project settings you'll see all the output from the server (going to the browser) in Debugview.

yu can add your own debugview statements in the code by calling;
p_web._trace('whatever')

The book has chapters on the overall flow and architechure.

And of course you can just read the browse, and form code to see where the code goes.

Cheers
Bruce

[Pauly]

I'd also like to see what's going on. I read the docs, and even bought the book - but am still challenged when it comes to knowing where (for example) to put some code that'll fire every time I do xxx... A hint sheet would do.. perhaps a list of the 'old' clarion embed points (remember them?) with the relative Nettalk one. I understand that may not be possible for all.
Pauly

[Pauly]

Seems we are not the only ones... Have a look at the Clarion.contracts.jobs newsgroup.. People are actually wanting to hire others to 'walk them through' techniques. I see an opportunity for Bruce here :-)
Pauly