[Implemented] Add a structure viewing window to the debugger
Posted: Thu Sep 26, 2002 7:10 pm
Restored from previous forum. Originally posted by Franco.
Hi Fred,
as the topic points out it would be nice to have it
Maybe in a TreeView thingy like:
I discovered a bug (again...) in my first attempt to write a game (nothing fancy), but I don't know if it's my fault (...bad code?), or in the sprite lib, or in the thread lib.
I suppose it's in one of these lib's, because the bug comes only on WinXP NOT on Win2000 (always when the game switches from the base-level to level 1, the cpu usage is jumping from 25% to 100% and remains there, from now on the keyboard input acts very slooow - as I said only on WinXP {Gill Bates: "every Windows program works the same on every Windoze platform" - [me] Yes, right... [/me])
Now because I use already 2 threads (this number will grow!) I use Structures a lot (to get the real actual values... for the threads) - and I can't see the values of it.
For now I have to build a procedure which collects all values from the structures and call it in the main loop - maybe I build another thread for that. This way I could see if there is a structure value messing around (...I have no idea why this should be and why it should interfere with the cpu usage, but I have to track down this bug).
And then, if the bug is really in a lib I'm lost again. But that is another story.
Please Fred, would you consider adding a TreeView Window for structures in the debugger
ADDITION:
I meant only user defined structures not all the API stuff...
Have a nice day...
Franco
Sometimes you have to go a lonely way to accomplish genius things.
Hi Fred,
as the topic points out it would be nice to have it
Maybe in a TreeView thingy like:
Code: Select all
+ Variable1.Structure1
Value1
Value2
etc...
+ Variable2.Structure2
Value1
Value2
etc...
I suppose it's in one of these lib's, because the bug comes only on WinXP NOT on Win2000 (always when the game switches from the base-level to level 1, the cpu usage is jumping from 25% to 100% and remains there, from now on the keyboard input acts very slooow - as I said only on WinXP {Gill Bates: "every Windows program works the same on every Windoze platform" - [me] Yes, right... [/me])
Now because I use already 2 threads (this number will grow!) I use Structures a lot (to get the real actual values... for the threads) - and I can't see the values of it.
For now I have to build a procedure which collects all values from the structures and call it in the main loop - maybe I build another thread for that. This way I could see if there is a structure value messing around (...I have no idea why this should be and why it should interfere with the cpu usage, but I have to track down this bug).
And then, if the bug is really in a lib I'm lost again. But that is another story.
Please Fred, would you consider adding a TreeView Window for structures in the debugger
ADDITION:
I meant only user defined structures not all the API stuff...
Have a nice day...
Franco
Sometimes you have to go a lonely way to accomplish genius things.