#MyWindow on YourScreen
26-Jun-88 19:23:37
Sb: #132041-#MyWindow on YourScreen
Fm: John Draper 76703,4322
To: Mike Berro 73267,3361
This message turned up in search, but its forum couldn’t be identified from the original transcript, so it may not be linked into its thread.
Mike,
That would definitely work. You could use SetFunction() to intercept the
call, save the registers, check for your QLens, putting it on another screen
if present, then restoring regs and calling the real CloseScreen. One caveat
though is that there are no conventions for the SetFunction() call, and if
someone else does a SetFunction to the same vector, you could get into a
situation where you could not safely restore the old vector. Consider the
scenario:
You call SetFunction, pointing the vector at your code.
I call SetFunction, pointing the vector at my code.
so far so good… I call your code at the end of my routine.
You call SetFunction to restore the old vector.
You unload your code, and the memory is used again by the system.
I call SetFunction to restore the old vector.
Problem: I have restored your vector, now pointing at ???.
Just some thoughts.
-larry