Re: [platform-debug-dev] Using Debug events to make label updates to obj

["Darin Wright" <Darin_Wright@xxxxxxx>]

For problem (1), there is a solution (and we have a bug). A debug CHANGE event can have one of two details - STATE or CONTENT. In this case, you are describing a STATE change, which should update the label of the changed element. However, there is a bug in the launch view, which performs a complete refresh instead of simply updating the label. I have filed a bug for this (http://bugs.eclipse.org/bugs/show_bug.cgi?id=22107).

Problem (2) is a larger issue. There is a related bug for this (http://bugs.eclipse.org/bugs/show_bug.cgi?id=1582). The general problem is when "resuming" in a tight loop with a breakpoint, the variables view does not retain its expanded state. Instead all stack frames are collapsed and this information is lost. This problem needs more discussion. The challenges are:
* creating a debug model independent solution
* maintaining the model/presentation seperation
* no breaking 2.0 API changes

Proposals are welcome.

Darin

boxall@xxxxxxxxxx Sent by: platform-debug-dev-admin@xxxxxxxxxxx 08/01/2002 10:37 AM Please respond to platform-debug-dev

To:        platform-debug-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-debug-dev] Using Debug events to make label updates to objects displayed in debug views

I have run into a situation where I need to send a DebugEvent.CHANGE event
but the side effects cause the variable's view to lose the state of
variable expansion.

My IDebugTarget's label changes often during a debug session to reflect the
state of the remote debug engine.    To get the label updated I get the
IDebugTarget to send a DebugEvent.CHANGE event.

Unfortunately, sending a change event for the debug target causes the
LaunchView to refresh the whole debug target and this results in a nasty
side effect.  A selection event gets generated that results in flashing in
other views that are listening for selection events.    The Variables view
in particular will lose the current expanded state of the variables it is
showing because it clears its cached values if the input changes.

I would like to make 2 suggestions...

1) I would like to be able to send a DebugEvent.CHANGE with a detail that
indicates that only the label of the element needs to be updated instead of
the complete refresh that occurs today.

2) I would like to see the expansion state of variables in the Variables
view kept in the IStackFrame.   This would allow a user to run to a
breakpoint in the same stackframe and keep any variable expansion that they
requested.   It would also all the user to select between different debug
targets and their stackframes and the expansion would be preserved.

Alan Boxall - IBM Distributed Debugger

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