On 07/03/2011 08:35, Norman Dunbar wrote:
Sigh!
Last night, I was doing some work on the "next exciting article" in the
Pointer Environment series of Assembly programming for Ql Today.
Basically, in the application window hit routine, I was attempting to
print out all the meaningful data about the registers when the routine
is called.
Try as I might, the keystroke in D2.B would not print, unless a special
case of -1, 0, 1 or 2.
I spent ages looking, tracing with JMON and so on, I could see the
keycode in D2.B but it simply refused to print when copied to D1.B.
I was using IO_SBYTE/IOB_SBYT to print the keycode. There were never any
errors seen after "printing" the keystroke as the trap always returned
with D0=0 and the Z flag set.
Eventually, I gave up and decided to pen a "help me" email to the list.
While doing exactly that, I typed in a bit of the code and suddenly
realised that I was a pillock! I was calling trap #1 rather than trap
#3 - instead of printing a byte to a channel, I was force removing a
(thankfully non-existent) job!
Duh!
Cheers,
Norman.
Norman,
It's an easy enough mistake - I am just glad that you were not entering
the job ID for the editor task - now that would have been a confusing
bug to track down!!
--
Rich Mellor
RWAP Services
http://www.rwapsoftware.co.uk
http://www.rwapservices.co.uk
-- Try out our new site: http://sellmyretro.com
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
