RE: stop trace ! :>)

new topic     » goto parent     » topic index » view thread      » older message » newer message

Ok !

Thanks for all. This solve the problem.


At 14:33 27/8/2002, you wrote:
>
>Hi Rubens,
>
>You must make sure that there are no "with trace" statements within the
>include file.  If you have a "without trace" before including the file
>but then the include file has a "with trace", then that will override
>the "without trace".
>
>Derek sometimes leaves in some "with trace" statements in Win32Lib for
>debugging...
>
>So clean out any "with trace" statements from includes that you don't
>want to see.  Then all you should have to do is:
>
>include Win32Lib.ew
>include database.e
>without warning
>with trace
>
>procedure
>    trace(1)
>    ...
>    trace(0)
>end procedure
>
>-- Brian
>
>
>Rubens wrote:
> > Hi Kat, Hi Andy;
> >
> >          You mean this:
> >
> >
> > without trace
> > include Win32lib.ew
> > include database.e
> > without warning
> > with trace
> >
> > procedure
> > trace(1)
> > ...
> > trace(0)
> > end procedure.
> >
> > Didn't work. If I had in this procedure some call to the database for
> > example, the trace window will show all the routines for the database.e
> >
> > Any ideas ?
> >
> >
> > Rubens
> >
> >
> > At 19:28 26/8/2002, you wrote:
> > >
> > >On 26 Aug 2002, at 19:11, rubis at fem.unicamp.br wrote:
> > >
> > > >
> > > > Hi people;
> > > >
> > > >
> > > >  How do I keep the trace window results only in my program, and not
> > > > "walking away" through the include files or win32lib ?
> > >
> > >Put the "with trace" and "trace(1)" AFTER all the includes. Then in the
> > >includes, put "without trace".
> > >
> > >Kat
> > >
> > >
>
>

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu