[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-debug-dev] launch config mapped resources
|
Nope. The types are contributed via an extension, and they are discovered
and shown without having to involve the delegate, just like actions. Only
when the user actually creates a launch configuration of the type (or
selects an existing one) does the plugin get loaded.
OK. I'll open a bugzilla report. Just thought I might be overlooking
something obvious. Thanks,
John
At 05:15 PM 4/20/2009, Michael Rennie wrote:
I just assumed that in step 6
when the user opens the launch dialog that CDT would be loaded (to load
the CDT launch configuration type(s)),
Is this not the case?
Maybe there is something better we could do in the platform. You should
open a bug for this.
Michael Rennie
John Cortell ---04/20/2009 05:01:48 PM---Thanks,
but I'm not sure how that would solve the use-case I detailed. CDT isn't
loaded at any point
![[]](jpgQHFbrxtUpc.jpg)
From:
John Cortell <john.cortell@xxxxxxxxxxxxx>
![[]](jpgQHFbrxtUpc.jpg)
To:
"Eclipse Platform Debug component developers
list." <platform-debug-dev@xxxxxxxxxxx>, "Eclipse
Platform Debug component developers list."
<platform-debug-dev@xxxxxxxxxxx>
![[]](jpgQHFbrxtUpc.jpg)
Date:
04/20/2009 05:01 PM
![[]](jpgQHFbrxtUpc.jpg)
Subject:
Re: [platform-debug-dev] launch config mapped
resources
Thanks, but I'm not sure how that would solve the use-case I
detailed. CDT isn't loaded at any point in the second instantation of
Eclipse (starting at step 4).
John
At 04:54 PM 4/20/2009, Michael Rennie wrote:
You could try adding CDT as a save participant
using:
ResourcesPlugin.getWorkspace().addSaveParticipant(ISaveParticipant)
You get back a delta of what has changed since the last time you
participated in a save (likely the last time your bundle was loaded).
This
way you can try processing the ISavedState object and performing updates
as needed (the next time CDT is
loaded).
As an example we add a participant for the DebugPlugin in its
start(BundleContext) method, although we don't do anything with the
ISavedState object returned from
addSaveParticipant(ISaveParticipant).
Michael Rennie
John Cortell ---04/20/2009 04:28:28 PM---The
ability to map a resource to a launch config was a great addition in 3.2.
But it introduces an
From:
John Cortell <john.cortell@xxxxxxxxxxxxx>
To:
"Eclipse Platform Debug component developers list."
<platform-debug-dev@xxxxxxxxxxx>
Date:
04/20/2009 04:28 PM
Subject:
[platform-debug-dev] launch config mapped resources
The ability to map a resource to a launch config was a great addition
in 3.2. But it introduces an interesting dilemma: how to deal with
resource name changes. The mappings don't get automatically updated.
One might think of registering a resource change listener, but what
if the resource change happens before the listening plugin is
loaded?
1. User launches Eclipse
2. User creates a CDT project and a launch config for it (CDT gives
the config a mapping to the Project)
3. User terminates Eclipse
4. User launches Eclipse
5. User renames the project
6. User opens launch configuration editor
The launch config is not shown. CDT has not been loaded at this
point, so even if it had a resource listener, it couldn't have done
anything.
Is there an obvious solution here, or a creative one?
John
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev