| Re: [cdt-dev] Launch bar 'stop' button kills all launches |
|
I would think they want it consistent. There's nothing special about debug. It should go back to the state things were in before they pressed build or launch.
Sent from my BlackBerry 10 smartphone on the Rogers network.
The strange thing is that the console stop button behaves the same as the debug ‘terminate’. I had never paid attention but that button must be retargeted just like the debug one.
So now I’m thinking that when doing a ‘Run’ launch, the ‘stop’ button from the launch bar needs to stop the run. Which is actually what the ‘terminate’ button also does. Same for ‘Profile’ I assume. The only issue is when debugging. So what does a user want the launch bar ‘stop’ to do during a debug session?
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer
Got to be careful. Your pretty close to debug :). The real question is what does a relative beginner expect. The launch bar is for much more than debug. If your just Running all the time which a lot of users do you need a way to stop the run. Usually you do that at the console. Same with stopping the build jobs. Those buttons are both red squares.
Sent from my BlackBerry 10 smartphone on the Rogers network.
“Build, Launch, and Stop”
Even by the naming, I feel the overlap. ‘Build’ and ‘Launch’ are good to me. ‘Stop’ makes me think of the debugging action.
While discussing it internally, it was suggested that the ‘Stop’ icon of the Launch bar could be a big X instead of a square. That could help distinguish ‘stop’ from ‘terminate’.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer
It was only temporary while waiting for the mapping from mode, descriptor, target to launch configuration settled down. We can probably do this correctly now.
But there are some benefits to having a button that stops everything. That's why I haven't been in a hurry to fix it. But you bring up great points so I'll have to give it more thought when I'm back from holidays.
If someone has better icons, we can look at that too. I thought they were sufficiently different from the ones in the Debug View (and yes, they belong in the debug view, not on the main trimbar) yet reflected the semantics which really are Build, Launch, and Stop, that it should help avoid confusion which it does a bit anyway.
Doug.
From:
cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Alena Laskavaia [elaskavaia.cdt@xxxxxxxxx] For killing launch I said "it used to". Doug changed it to kill all with idea to review with community I am guessing. Play button did give me trouble before when debugging. I was always trying to press it instead of resume, and that would re-launch whole app which was quiet annoying when you just trying to resume :) Terminate would do the same as debug terminate (mostly) - so it was not an issue (it will terminate launch associated with selection, at least it used to)
Current actions are Build - build project associated with LC, even build before launch is disabled in LC Launch - create lc is none for selected desc, launch lc in the selected mode Stop - stop all builds, terminate all launches (for now)
On Fri, Aug 1, 2014 at 10:27 AM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote: > We use to kill only launch which is associated with active launch configuration.
Is that what the Launch Bar in CDT is doing? I don’t see that. If I launch a “C/C++ Attach to Application” and a “C/C++ Application” sessions and press the launch stop button, they both die.
To me, one thing that seems relatively straightforward is that the button should kill the currently selected launch, not all launches. I don’t think there is much value in killing all launches (and there is a “Terminate/Disconnect all” context menu for that, if really needed). How about we start with that?
Now, if we go into more details, the thing to note is that the Launch Bar buttons are ‘launch’ buttons, not ‘run/debug’ buttons. So the launch ‘play’ button is very different than the debug ‘resume’ button, although they have a similar-looking icon. I didn’t find that distinction hard to get used to for the ‘play’ button.
On the other hand, the launch ‘stop’ button and the run/debug ‘terminate’ button gave me more trouble. For some reason, as a user, I thought the launch ‘stop’ could be used as ‘terminate’, which is not true for Debugging. ‘terminate’ is a retargetable command that different debuggers use differently; CDT’s debugger allows you to terminate the process without terminating the debug session. The launch ‘stop’ is not the same and probably should not be; but I think we may have a UX issue here because that distinction was not obvious to me. Maybe it is simply a question of changing the icon? Do other agree with my impression?
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Alena Laskavaia
We use to kill only launch which is associated with active launch configuration. Build it kills all builds because that we cannot really associate (project dependency and stuff)
On Mon, Jul 28, 2014 at 3:54 PM, Doug Schaefer <dschaefer@xxxxxxx> wrote: Not sure yet. What do you think it should do?
The strange thing is that the console stop button behaves the same as the debug ‘terminate’. I had never paid attention but that button must be retargeted just like the debug one.
So now I’m thinking that when doing a ‘Run’ launch, the ‘stop’ button from the launch bar needs to stop the run. Which is actually what the ‘terminate’ button also does. Same for ‘Profile’ I assume. The only issue is when debugging. So what does a user want the launch bar ‘stop’ to do during a debug session?
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer
Got to be careful. Your pretty close to debug :). The real question is what does a relative beginner expect. The launch bar is for much more than debug. If your just Running all the time which a lot of users do you need a way to stop the run. Usually you do that at the console. Same with stopping the build jobs. Those buttons are both red squares.
Sent from my BlackBerry 10 smartphone on the Rogers network.
“Build, Launch, and Stop”
Even by the naming, I feel the overlap. ‘Build’ and ‘Launch’ are good to me. ‘Stop’ makes me think of the debugging action.
While discussing it internally, it was suggested that the ‘Stop’ icon of the Launch bar could be a big X instead of a square. That could help distinguish ‘stop’ from ‘terminate’.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer
It was only temporary while waiting for the mapping from mode, descriptor, target to launch configuration settled down. We can probably do this correctly now.
But there are some benefits to having a button that stops everything. That's why I haven't been in a hurry to fix it. But you bring up great points so I'll have to give it more thought when I'm back from holidays.
If someone has better icons, we can look at that too. I thought they were sufficiently different from the ones in the Debug View (and yes, they belong in the debug view, not on the main trimbar) yet reflected the semantics which really are Build, Launch, and Stop, that it should help avoid confusion which it does a bit anyway.
Doug.
From:
cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Alena Laskavaia [elaskavaia.cdt@xxxxxxxxx] For killing launch I said "it used to". Doug changed it to kill all with idea to review with community I am guessing. Play button did give me trouble before when debugging. I was always trying to press it instead of resume, and that would re-launch whole app which was quiet annoying when you just trying to resume :) Terminate would do the same as debug terminate (mostly) - so it was not an issue (it will terminate launch associated with selection, at least it used to)
Current actions are Build - build project associated with LC, even build before launch is disabled in LC Launch - create lc is none for selected desc, launch lc in the selected mode Stop - stop all builds, terminate all launches (for now)
On Fri, Aug 1, 2014 at 10:27 AM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote: > We use to kill only launch which is associated with active launch configuration.
Is that what the Launch Bar in CDT is doing? I don’t see that. If I launch a “C/C++ Attach to Application” and a “C/C++ Application” sessions and press the launch stop button, they both die.
To me, one thing that seems relatively straightforward is that the button should kill the currently selected launch, not all launches. I don’t think there is much value in killing all launches (and there is a “Terminate/Disconnect all” context menu for that, if really needed). How about we start with that?
Now, if we go into more details, the thing to note is that the Launch Bar buttons are ‘launch’ buttons, not ‘run/debug’ buttons. So the launch ‘play’ button is very different than the debug ‘resume’ button, although they have a similar-looking icon. I didn’t find that distinction hard to get used to for the ‘play’ button.
On the other hand, the launch ‘stop’ button and the run/debug ‘terminate’ button gave me more trouble. For some reason, as a user, I thought the launch ‘stop’ could be used as ‘terminate’, which is not true for Debugging. ‘terminate’ is a retargetable command that different debuggers use differently; CDT’s debugger allows you to terminate the process without terminating the debug session. The launch ‘stop’ is not the same and probably should not be; but I think we may have a UX issue here because that distinction was not obvious to me. Maybe it is simply a question of changing the icon? Do other agree with my impression?
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Alena Laskavaia
We use to kill only launch which is associated with active launch configuration. Build it kills all builds because that we cannot really associate (project dependency and stuff)
On Mon, Jul 28, 2014 at 3:54 PM, Doug Schaefer <dschaefer@xxxxxxx> wrote: Not sure yet. What do you think it should do?
| ||||