Re: [platform-debug-dev] Behaviour of variable expansion

[Darin_Wright@xxxxxxx]

I hestiate to add a method to the "headless" debug model that deals directly with presentation. Generally, methods/attributes on our model objects represent state that the presentation can take advantage of, but the model objects themselves do not directly control the presentation.

We need to look at this problem in more detail. Perhaps it is really related to the problem that the variable view collapses variables on thread resumes, when it should try to maintain its expanded state.

Darin

boxall@xxxxxxxxxx Sent by: platform-debug-dev-admin@xxxxxxxxxxx 03/28/2002 01:19 PM Please respond to platform-debug-dev

To:        platform-debug-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-debug-dev] Behaviour of variable expansion

One of the plugins we are building has a usability problem with collapsed
variables.

Some variables are global and therefore appear in the Variables view for
every selected stackframe.

These globals tend to be complex and to be useful, the user must expand
them.

The problem is that they are always being collapsed because the stackframes
change on step, run etc. forcing the user to expand these globals after
every step, run etc.

We know that the debug core won't be able to remember expansion of
variables because the stackframes are changing ...

so...

we have a suggestion to help with complex variables.   Add the notion of
"autoExpand" to the variable.   This would allow the debug plugins to
dictate to the variables view that it should expand this variable.

Something like:
     boolean IVariable.autoExpand()

     where "true" means that the Variable view should force expansion of
this variable.

Alan Boxall - IBM Distributed Debugger

_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-debug-dev