VC6 debug variables window - "auto" not workin
by Orion Elenzil · in Torque Game Engine · 09/01/2004 (3:25 pm) · 4 replies
In the treasured 'variables' window of VC6,
where variables & objects can be explored during debugging,
the "auto" tab doesn't work for me w/ the torque engine.
the "Local" and "this" tabs work as usual,
as does mousing over a variable or quickwatch.
Anyone else seen this ?
I'm using whole tomato's Visual Assist X,
altho i doubt that's the issue.
where variables & objects can be explored during debugging,
the "auto" tab doesn't work for me w/ the torque engine.
the "Local" and "this" tabs work as usual,
as does mousing over a variable or quickwatch.
Anyone else seen this ?
I'm using whole tomato's Visual Assist X,
altho i doubt that's the issue.
About the author
#2
yeah, well 'auto' is definitely what i find most useful,
but if you click the "locals" tab, there's all the variables in local scope,
and if you mouse over a variable or expression up in the source (ie "mesh->verts[0]" or somesuch) you can right-click and then choose "quickwatch" and from there choose "add watch", and you get a nice little variable explorer.
you can even modify your C++ code and then continue execution in VC -
just turn on 'enable incremental compilation' in Project Settings | C/C++ | Customize.
VC's debugger is definitely one thing microsoft did right, IMO.
especially after i spent some time recently w/ unix's gdb.
09/01/2004 (4:17 pm)
Heh.yeah, well 'auto' is definitely what i find most useful,
but if you click the "locals" tab, there's all the variables in local scope,
and if you mouse over a variable or expression up in the source (ie "mesh->verts[0]" or somesuch) you can right-click and then choose "quickwatch" and from there choose "add watch", and you get a nice little variable explorer.
you can even modify your C++ code and then continue execution in VC -
just turn on 'enable incremental compilation' in Project Settings | C/C++ | Customize.
VC's debugger is definitely one thing microsoft did right, IMO.
especially after i spent some time recently w/ unix's gdb.
#3
If there's nothing there, just fall back to the local tab.
09/04/2004 (12:20 pm)
The auto tab tries to guess what variables are being used currently in the code... and it can guess wrong or fail to guess. TGE might be too complex for it. :PIf there's nothing there, just fall back to the local tab.
#4
but generally Auto works for basic member & even local variables.
I just hoped this was a known thing with a "oh just check suchnsuch" to go along with.
Locals it is!
Also mouse-over & quickwatch work,
which go a long way.
09/08/2004 (8:58 am)
Heh. Yeah, it can get confused by tricky #defines or templates etc,but generally Auto works for basic member & even local variables.
I just hoped this was a known thing with a "oh just check suchnsuch" to go along with.
Locals it is!
Also mouse-over & quickwatch work,
which go a long way.
Torque Owner Ace
So i never use debug.
i have vc6.0 and xp