| Re: [cdt-dev] CMainTab ui |
|
Yeah, I'm 100% sure these don't make sense. Both of these modes should have their own launch delegates to manage the distince ways in which they launch. The should also have their own Tabs that control options specific to them.
Oh, yeah, and I guess I should point out that they should be different launch modes.
It all becomes more obvious when you use the launch bar for launching.
Doug.
From: Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>
Date: Wed Oct 29 2014 12:35:49 GMT-0400 (EDT) To: 'CDT General developers list.' <cdt-dev@xxxxxxxxxxx> Subject: Re: [cdt-dev] CMainTab ui Another good point. This makes sense for CDT itself and I would like to see it there. If you provide the change for CDT, I’ll review it and everyone’s life will become better J
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin
Hi all,
It’s interesting that I stumbled over CMainTab & Build-before-launch just today in some slightly different context – good to have that discussion right now J
I found that the “Build (if required) before launching” group is visible in the “Attach” and “PostMortem” launches as well. Now I’m 99.9% sure that building a project before analyzing a coredump does not make sense. And I am 80% sure that building a project before attaching does not make sense.
Is there a way we could get the entire “Build before launch” section hidden in our product ? Or have it moved to a separate tab such that the main tab is focused on what’s really relevant ?
Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Alena Laskavaia
I would like to get rid of extra checkbox in CMainTab ui for build config selector called "Select configuration using 'C/C++ Application'" and move it to Combo instead
This is how it looks now
What I am proposing is this:
So "Auto" in this case is same choice as previous checkbox but it uses less space It also by discretion of the launch config delegate to interpret this value and pick configuration based on some other logic (rather then application path only) Thoughts?
(Note: this button is API unfortunately, so I am planning to keep it but make invisible, |
