Difference between revisions of "83Plus:Hooks:9BBC"
From WikiTI
m |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:83Plus:Hooks:By_Name|cxRedisp Hook]] [[Category:83Plus:Hooks:By_Address|9BBC - cxRedisp Hook]] | ||
== Synopsis == | == Synopsis == | ||
'''Name:''' cxRedisp ''(has been incorrectly called the PutAway hook)'' | '''Name:''' cxRedisp ''(has been incorrectly called the PutAway hook)'' | ||
| Line 10: | Line 11: | ||
'''Hook Call BCALL:''' ''(Unknown)'' | '''Hook Call BCALL:''' ''(Unknown)'' | ||
| − | '''Hook Active Flag:''' 5, (iy + 36h) | + | '''Hook Active Flag:''' [[83Plus:Flags:36#Bit_5|5, (iy + 36h)]] |
| − | == Hook | + | == Using the Hook == |
| − | This hook is a very simple, but very useful one. It's triggered before the system monitor calls cxRedisp for any context. Both the A and B registers will contain the current context (basically the value of cxCurApp.) Returning with the zero flag set will cause the cxRedisp vector to be called; returning with it reset will prevent the vector from being called (this will generally break any system context!) | + | This hook is a very simple, but very useful one. It's triggered before the system monitor calls cxRedisp for any context. Both the A and B registers will contain the current context (basically the value of [[83Plus:RAM:859A|cxCurApp]].) Returning with the zero flag set will cause the cxRedisp vector to be called; returning with it reset will prevent the vector from being called (this will generally break any system context!) |
Latest revision as of 21:14, 29 March 2005
Synopsis
Name: cxRedisp (has been incorrectly called the PutAway hook)
Hook Pointer Block Address: 9BBCh
Hook Enable BCALL: 506Bh
Hook Disable BCALL: 506Eh
Hook Call BCALL: (Unknown)
Hook Active Flag: 5, (iy + 36h)
Using the Hook
This hook is a very simple, but very useful one. It's triggered before the system monitor calls cxRedisp for any context. Both the A and B registers will contain the current context (basically the value of cxCurApp.) Returning with the zero flag set will cause the cxRedisp vector to be called; returning with it reset will prevent the vector from being called (this will generally break any system context!)
