Hi George, > 1. The expected use of the hit routine is to call WM_MHIT by JMP WM_MHIT(A2). Yes, I read that - I don't understand why, if this is the case, I can have a hit routine that is expected to jump back into the WMAN code to handle it internally. Why not just call WM_MHIT internally anyway?
> 2. The manual says that WM_RPTR does, among a lot of other things - > "if in application window > call hit routine > next read pointer" > > A program in which ahit0 prints "HIT" on a "hit" (SPACE) and resets the > application window on a "DO" (ENTER) but ignores everything else looks normal > in execution but shows the constant reentering of ahit0 when run under QMON. Yes, My original posting showed a test hit routine that I am using. It shows exactly how many times the hit routine is called for an application sub-window! Just moving the pointer over the window causes a lot of hits! Still, I'm learning new stuff! I suppose that a PE application could be written in such a way as to use a SCR_ channel for normal program output (my HIT counter for example) rather than using a dedicated sub-window, however, I'm not sure what would happen if I did so, and then moved it around the screen! I have a funny feeling I'd end up still writing to the previous location! Maybe an information window would be a better idea. Worth investigating I suspect. Cheers, Norman. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: Thorpe House 61 Richardshaw Lane Pudsey West Yorkshire United Kingdom LS28 7EL Company Number: 05132767 _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
