Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.acorn.programmer > #493 > unrolled thread

Using !Reporter with Wimp Program

Back to article view | Back to comp.sys.acorn.programmer

Contents

  Using !Reporter with Wimp Program cferris@freeRemoveuk.com.invalid - 2011-07-01 10:42 +0100
    Re: Using !Reporter with Wimp Program Paul Sprangers <Paul@sprie.nl> - 2011-07-01 14:20 +0200
    Re: Using !Reporter with Wimp Program Martin <News03@avisoft.f9.co.uk> - 2011-07-01 13:42 +0100
      Re: Using !Reporter with Wimp Program cferris@freeRemoveuk.com.invalid - 2011-07-01 14:44 +0100
        Re: Using !Reporter with Wimp Program Martin <News03@avisoft.f9.co.uk> - 2011-07-01 15:39 +0100

#493 — Using !Reporter with Wimp Program

What is the best method of using !Reporter with a BASIC Wimp program?

ie - a way of avoiding showing all the WimpPoll returns.

Thanks
-- 
Colin Ferris Cornwall UK

[toc] | [next] | [standalone]

#494

In article <3634e8eb51.cferris@cferris.freeuk.com>,
   <cferris@freeRemoveuk.com.invalid> wrote:

> What is the best method of using !Reporter with a BASIC Wimp program?
> ie - a way of avoiding showing all the WimpPoll returns.

As far as I know, you will only see all those WimpPoll returns if you use
Reporter within the poll loop. When used within a routine, it will
obviously only return something when the routine is called.

Without more information, it is hard to guess what you are after, but if
you want to know the value of a particular variable, say var$, you should
enter a line after the one where var$ is set or changed, typically
*report var$

The accompanying StrongHelp manual will guide you through its features.
Anyhow, Reporter is at least as priceless as StrongHelp itself, I think.

Kind regards,
Paul Sprangers

[toc] | [prev] | [next] | [standalone]

#495

On 01 Jul, in article <3634e8eb51.cferris@cferris.freeuk.com>,
   <cferris@freeRemoveuk.com.invalid> wrote:
> What is the best method of using !Reporter with a BASIC Wimp program?

> ie - a way of avoiding showing all the WimpPoll returns.

Reporter will only report what it has been asked to do!

If you have some *Report commands that get processed every Wimp Poll, you
will see how often your program is polled! You can ... 
- remove/comment the *Report commands, 
- move them to where you DO want to know about 
- mask out the Null reason code (should always do unless needed)
- change to PollIdle with a larger delay time!

I use Reporter extensively here (but then I would!) for debugging a
30,000 line Basic program with hundreds or *Report commands, but usually
I do not have any within the Null Poll code unless I REALLY need them.

Martin

-- 
Martin Avison 
Note that unfortunately this email address will become invalid
without notice if (when) any spam is received. 

[toc] | [prev] | [next] | [standalone]

#496

In message <51ebf8bae2News03@avisoft.f9.co.uk>
          Martin <News03@avisoft.f9.co.uk> wrote:

> On 01 Jul, in article <3634e8eb51.cferris@cferris.freeuk.com>,
>    <cferris@freeRemoveuk.com.invalid> wrote:
> > What is the best method of using !Reporter with a BASIC Wimp program?
> 
> > ie - a way of avoiding showing all the WimpPoll returns.
> 
> Reporter will only report what it has been asked to do!
> 
> If you have some *Report commands that get processed every Wimp Poll, you
> will see how often your program is polled! You can ... 
> - remove/comment the *Report commands, 
> - move them to where you DO want to know about 
> - mask out the Null reason code (should always do unless needed)
> - change to PollIdle with a larger delay time!
> 

Thanks for a very handy program.

I've a program here which seems to run ok with the RPC but locks up the
Iyonix.

Trying to pin the fault down - if I turn on PROC at the beginning of
the prog - then adding a *reportOn/Off for each of the poll jump tables
I interested in.
Tricky when the computer locks up - because getting near to the problem
PROC or LINE number info is lost. :-(

I was looking at the BASIC 'TRACE TO filename' - and storing the info
on local HD or whether a copy of the info be passed over the Ethernet
to annother computer.

Bye
-- 
Colin Ferris Cornwall UK

[toc] | [prev] | [next] | [standalone]

#497

On 01 Jul, in article <e15afeeb51.cferris@cferris.freeuk.com>,
   <cferris@freeRemoveuk.com.invalid> wrote:

[Snip]

> I've a program here which seems to run ok with the RPC but locks up the
> Iyonix.

When you say lockup, do you mean it needs a Reset/Power Off, or will
Alt-Break stop it?

> Trying to pin the fault down - if I turn on PROC at the beginning of
> the prog - then adding a *reportOn/Off for each of the poll jump tables
> I interested in.
> Tricky when the computer locks up - because getting near to the problem
> PROC or LINE number info is lost. :-(

Always nasty getting close to such problems!

If you can add a *ReportLogOn command into you program as close to the
problem as you can (or even at the beginning!) it will write the Reported
info to disc - AND it makes sure it is on the disc before continuing. See
!Help for further details. It will slow your program down, but that is a
small prioce to pay if it speeds your debugging!

> I was looking at the BASIC 'TRACE TO filename' - and storing the info
> on local HD or whether a copy of the info be passed over the Ethernet
> to annother computer.

Do not use Basic TRACE and *ReportTrace commands, they do not mix!
Everything the Basic TRACE command can do (well, almost all) can be done
with *ReportTrace, and you can write to a file (see above).

If you want any more specific help, please contact me directly.

Martin

-- 
Martin Avison 
Note that unfortunately this email address will become invalid
without notice if (when) any spam is received. 

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.acorn.programmer

csiph-web