>>[snip]>The most important being that I built a procedure that lets me print anything to a form with an editbox on it instead of using "? blah blah blah" (it's too annoying moving all my other open windows just to see the output of a ? statement).
>>
>>You can use CTRL+ALT+SHIFT to hide all open windows temporarily to view the ? output.
>
>Didn't know that one. Thanx. The only other reason that I would want to do what I was saying before is so that I could maybe copy the result to clipboard or scroll through the output. Any other ideas?
>
>Phillip
What I've got is a startup procedure that simply has
keyboard 'do d:\walpole\startup{ENTER}'
This writes the call to my custom
startup
to the Command window and executes it.
Inside
startup
I set all kinds of stuff (paths, DLLs declares, etc.) and create a public instance of a tools class.
With the call to the fully qualified path to
startup
, whatever directory I'm in, whatever the objects in memory, etc., etc., I can simply hit
CTRL+HOME
while in the Command window to move to the top line, which is always the call to
startup
since I don't clear my command window. If I ever need to clear it, I just go to the top line, copy that first, clear the Command window, paste and execute
startup
again.
HTH
Insanity: Doing the same thing over and over and expecting different results.