| Re: [cdt-dev] Getting active launch target for a descriptor |
_______________________________________________I’m certainly open to patches to adjust the API, or at least add to it. We started the Launch Bar with an idealistic view of the workflows, in particular, that the launch bar UI was the only way you changed the active selections. In the IDEs we were emulating, that was how you managed configs. But I’m certainly open now to be more pragmatic about things as we try to integrate with other tools.
Feel free to raise a bug and we can have the discussion there and see if we can come up with something.
Doug.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Waqas Ilyas
Sent: Wednesday, March 28, 2018 10:40 PM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Getting active launch target for a descriptor
Hi Doug,
Thanks for the hint, I'll have a look.The problem I am facing is that a user may change the "active" target from other places then just the launchbar. In which case I would like the launch bar to update and show the latest active target. I tried setting LaunchTargetManager.setDefaultLaunchTarget(..) when a user commits changes but it did not work. This is because the LaunchBarManager.syncActiveTarget() prefers its stored value.
If the launch bar is not really meant to keep this system wide information then perhaps it should use providers to fetch the active target for any descriptor that is being made active. Alternatively, if it prefers its own storage then perhaps there should be a way to modify the active selections.
Maybe one way is that I can use the LaunchBarManager to set active descriptor, target, and mode of my choosing every time a user commits it in some other dialog. Although not ideal as it changes user's active descriptor selection, but this might be one way. What do you suggest here?
Regards,
Waqas
On Tue, Mar 27, 2018 at 10:33 AM Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> wrote:
In general, the launch bar was never meant to be a system wide keeper of such knowledge. It’s just a UI element and we only kept that data because we wanted the selections to make sense when you switched back and forth. And, in the end, it’s really just a band-aid over the poor UX of Eclipse’s launch system.
Having said that, we do similar things with CDT’s core build where we want to set the active build configuration based on selections of the launch bar. Take a look at CDT’s CoreBuildLaunchBarTracker. You’ll need to manage this state yourself but at least the launch bar can give you clues.
Doug.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Waqas Ilyas
Sent: Monday, March 26, 2018 7:19 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Getting active launch target for a descriptor
Hi,
I am trying to hook in my delegates and launch configurations with the launch bar, and I have a question. How do I get the saved launch target last selected for a launch descriptor?
I am not looking for the active launch target, at any given time. I am looking for the active launch target for a descriptor that may itself not be active anymore. Is there a way to get this information from the launch manager?
Or do i have to set up a listener and maintain my own list?
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev