Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Small problem with Immediate window
- Thread starter Sika2
- Start date
JeffTullin
Programmer
Immediate is the debugging window.
It is here that the output from debug.print will appear if you have used debug statements in your code.
If it is showing up as free-floating, you have at some point dragged it away from it's docking area in the VB IDE.
Try dragging it by the window title, down to the bottom of the IDE window, where it should dock once more and stop bothering you.
It is here that the output from debug.print will appear if you have used debug statements in your code.
If it is showing up as free-floating, you have at some point dragged it away from it's docking area in the VB IDE.
Try dragging it by the window title, down to the bottom of the IDE window, where it should dock once more and stop bothering you.
The immediate window is actually very useful for debugging.
When you're at a breakpoint, you can inspect variables (even private ones in a class) by printing them:
You can even call some functions inside it:
You can also (sometimes) create small programs by using the colon operator to separate statements.
(I is assumed to be a variant -- note that there's no DIM statement for it).
Chip H.
If you want to get the best response to a question, please check out FAQ222-2244 first
When you're at a breakpoint, you can inspect variables (even private ones in a class) by printing them:
Code:
? oMyClass.oPrivateDOM.xml
Code:
? Len(oMyClass.oPrivateDOM.xml)
Code:
For I = 1 to 10 : Debug.Print i : Next IChip H.
If you want to get the best response to a question, please check out FAQ222-2244 first
- Status
