Re: [platform-debug-dev] Disconnect command

[Darin Wright <Darin_Wright@xxxxxxxxxx>]

I suspect this is just an oversight in the standard model. The Java 
debugger gets around this by having all its debug elements implement 
IDisconnect - such that the action works for any selected element. Other 
models could do the same, or model elements could provide IDisconnect 
adapters to get around this.

Darin 



From:
John Cortell <john.cortell@xxxxxxxxxxxxx>
To:
"Eclipse Platform Debug component developers list." 
<platform-debug-dev@xxxxxxxxxxx>
Date:
04/23/2009 02:28 PM
Subject:
[platform-debug-dev] Disconnect command
Sent by:
platform-debug-dev-bounces@xxxxxxxxxxx



In the Standard Debug Model, why is Disconnect supported only by 
IDebugTarget? That may indeed be the only context that the action directly 
makes sense for, but it is a pain for the user to have to make a selection 
change in order to access the function. The vast majority of time, the 
active debug context is a frame object. And just as terminating a frame 
doesn't make much sense  (you terminate a thread, or a process), the 
action is available on a frame object, and of course the implementation 
terminates the thread (or process) that frame belongs to. Why is 
Disconnect not treated the same way?

John_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev