home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!ub4b!news.cs.kuleuven.ac.be!blekul11!frmop11!dearn!esoc!smartin
- Organisation: European Space Operation Centre (E.S.O.C)
- Date: Tuesday, 10 Nov 1992 11:38:18 CET
- From: <SMARTIN@ESOC.BITNET>
- Message-ID: <92315.113818SMARTIN@ESOC.BITNET>
- Newsgroups: comp.sys.acorn.tech
- Subject: Re: Receiving message 0x502, and win' Work Area flags...
- References: <1992Nov3.095730.10327@westminster.ac.uk>
- <1992Nov9.005325.24603@cs.aukuni.ac.nz>
- Lines: 26
-
- In article <1992Nov9.005325.24603@cs.aukuni.ac.nz>, jwil1@cs.aukuni.ac.nz
- (TMOTA) says:
- >An easy test to do is to put a debugging 'printf' into your message handler
- >and print out the recieved message numbers... I use
- >
- >bbc_vdu(26); bbc_vdu(4); /* get the cursor in VDU4 mode at top left of scren*/
- >printf("Message number: %x", blah);
- >
- >or you could just use the printf, and redirect your programs output to
- >a file
- >(in !Run, change
- > Run <Obey$Dir>.blah
- >to
- > Run <Obey$Dir>.blah > <Obey$Dir>.output
- >)
- >
- >This way, you'll know *what* messages you're actually recieving, which is
- >always a good place to start working out why nothing's happening...
-
- How about using fprintf ? I always find this much simpler.
-
- -----------------------------------------------------------------
- Stuart Martin (Logica at ESOC) smartin@esoc.bitnet
-
- Any opinions expressed in the above posting are in no way intended to
- represent the official opinions of either Logica or ESOC.
-