I'm frustrated when I am debugging (using breakpoints and stepping through the code) and cannot link anything I see with anything in the mission model. TaskIDs, Topics, ConditionIDs, the many other IDs, and lambdas leave me lost. Actually, almost all objects you might be looking at in the debugger have no recognizable context : Cells, Resources, Tasks.
Describe the feature request
I want situational awareness in the IDE.
One possible low-hanging fruit is a collection of hash maps that can look up these IDs, lambda functions, and objects and tell me what they are. Lambda functions might be a challenge--maybe instrument the code to capture FILE, LINE, and method? Or, give the mission modeler the option to name all of these things and auto-generate names. David Legg's resource framework has a Naming class that does some of this.
What if all of these classes had a name field, including TaskID?
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
I'm frustrated when I am debugging (using breakpoints and stepping through the code) and cannot link anything I see with anything in the mission model.
TaskID
s,Topic
s,ConditionID
s, the many other IDs, and lambdas leave me lost. Actually, almost all objects you might be looking at in the debugger have no recognizable context :Cell
s,Resource
s,Task
s.Describe the feature request
I want situational awareness in the IDE.
One possible low-hanging fruit is a collection of hash maps that can look up these IDs, lambda functions, and objects and tell me what they are. Lambda functions might be a challenge--maybe instrument the code to capture FILE, LINE, and method? Or, give the mission modeler the option to name all of these things and auto-generate names. David Legg's resource framework has a
Naming
class that does some of this.What if all of these classes had a
name
field, including TaskID?