The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
What are you doing here?
Who forgot to close the fence of the insider?
run and duck
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
I have a number of objects in some apps with numerous variables and objects in them. When in the debugger, I'm usually only interested in a few values (bIsThisIncluded being the one I wish I could see). Unfortunately, when I mouse over to see what their values are I usually have to scroll down to see the value I want to know about. Is there any way to make them appear at the top of the list? It's not alphabetic. I've moved them around in my class declaration. I just wish I could get a few to appear at the top. Any ideas? Thanks, Mike
Ok. I guess. I work in the debugger every day at various levels of complexity and I have never in my career needed to do extra code to get things done like that. I guess your situation calls for it. so be it.
debugger has never been scary for me. knock on wood.
I just mean the visual studio live debugger integration.
it has never been particularly friendly.
using the debugger is friendly, and so are certain operations like Debug.WriteLine and Debugger.IsAttached, but to create "views" for objects beyond really simple things can often require custom code.
It's just that most people never really need to do it. The question in the OP is one that just doesn't come up that often in the real world. As those often can be, the solution is arcane. It's one of those dark corners of the debugger most people never need to touch.
How many people need to filter items in a collection or dictionary at debug time only?
Fortunately it's not a lot of code. The meat of it is in a single short method.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
The debugger I wrote was a companion to the script language compiler I also wrote. It wasn't just merely a script language though - it compiled to native machine code and it was pretty fast. Writing those was some of the most fun I have ever had programming. It was also very tricky, hence the lack of hair. Sometimes, when I am feeling particularly masochistic, I think about what I would do differently. Then I remind myself that it's not my problem any more.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
I use Oz Code debugger extension - I love all the things it does. It even predicts future events that can cause bad things to happen and warns you before your debugging pointer gets there....
A human being should be able to change a diaper, plan an invasion, butcher a hog, navigate a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects! - Lazarus Long