Re: [platform-debug-dev] contextual launch question
I like the idea of trying to better resolve the selection, or fall back to a previous selection.
There have always been some rough edges in context launching where we just give up because we have lost track of what you were doing or if a view (as you mentioned) does not provide a selection we can use.
I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=413752 to discuss enhancing context launching to make the process smoother.
"Alexiev, Dobrin" ---24/07/2013 06:08:12 PM---Hello, This is a question about the contextual launcher.
From: "Alexiev, Dobrin" <dalexiev@xxxxxx>
To: "platform-debug-dev@xxxxxxxxxxx" <platform-debug-dev@xxxxxxxxxxx>
Date: 24/07/2013 06:08 PM
Subject: [platform-debug-dev] contextual launch question
Sent by: platform-debug-dev-bounces@xxxxxxxxxxx
This is a question about the contextual launcher.
When I select a source editor and click the “debug” toolbar button a correct debug session is created based on my source editor.
When my source editor is the active editor but the active workbench part is the Console View, selecting the “Debug” toolbar button popup a dialog saying: “The selection cannot be launched, and there are no recent launches.”.
I was expecting the debug session to start based on my top most source editor.
I understand that any view can provide a structured selection and the different launch providers will consider that selection to create launches.
But if the current active part does not provide a structured selection, does it makes sense to remember the most recently activated part, that does have a structured selection and ask the launch providers to create launches based on that part and its most recent selection?
platform-debug-dev mailing list