- Improving on the debugger output window
Would you be kind enough to explain what do you want to improve there?
Edit: That should probably have read "Debugger variables output window" instead.
I am not sure if there already is someone doing things there. But, lately I have been using the debugger quite a lot. Due to a sloppy style of programming, which may not be the most efficient. Nevertheless, I had the feeling that it could be improved, but I am not sure. Something that hit me was that function variables and variables in scope is automatically added, which slows down (just a little bit). They could perhaps be defaulted to not being shown. I am not sure if there is an opposite opinion about this. Then there was that I tried to change the type of display for a variable, which I in the rush could not find how to do.
Then I had another idea, which seems to be more advanced and perhaps a little too much. And that would be to be able to create a more advanced display of a variable. For example I had a class that stored a pointer, but which always for some design reason, were shifted up 3 bits. To get the actual pointer from that member variable I had to use a calculator every time to shift down 3 bits to see the value. If a display of a variable could be preprocessed like so (SomeClass.mPointer >> 3). I have no clue how difficult it would be to implement or how valuable that could be.