ken.ryall@xxxxxxxxx wrote:
Pawel,
Thanks, now I see how IModelSelectionPolicy.isSticky works. But it
looks like isSticky is only given the existing selection and not the
new candidate selection to evaluate. I wanted to make the isSticky
decision based on the new candidate selection. Am I missing something?
Is sticky is only called when determining whether selection should be
changed between different debug models (e.g. CDT debugger has current
selection, but a JDT debugger has suspended). override(), which
contains both old and new selections, is called when both elements
belong to the same debug model (and use the same selection policy).
In DSF-GDB, we create a separate selection policy for each separate DSF
session, so isSticky() is called if the selection candidate is in a
different session (and ususally launch). To overcome this, what you
could do is have a single selection policy for all EDC (or even all
DSF) debug sessions, then you could use override() to decide whether
selection should be changed.
BTW, I'm guessing that you are trying to address the same problem as
bug 262260 is: notify the user through the Debug view that something
has happened when he issues a launch.
Cheers,
Pawel
Thanks - Ken
From: ext Pawel Piech
<pawel.piech@xxxxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Wed, 3 Feb 2010 00:38:40 +0100
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Behavior of Debug View on DSF Suspend
Hi Ken,
Take a look at IModelSelectionPolicyFactory (and
DefaultDsfModelSelectionPolicyFactory).
Cheers,
Pawel
ken.ryall@xxxxxxxxx
wrote:
Behavior of Debug View on DSF Suspend I need
a hint from someone more familiar with the way the DSF debug view model
works:
It looks like if you launch a debug session and suspend execution the
suspended context is properly revealed and selected in the Debug view.
Then if you launch a new second session and suspend execution it seems
to decide not to reveal or select the newly suspended context. This may
be the right thing to do in most cases but I have one where I want the
latest suspended context to be revealed and selected in the debug view
each time.
Can someone point me in the right direction?
Thanks - Ken
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
