Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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
Sent: Wednesday, October 29, 2014 11:57 AM
To: elaskavaia.cdt@xxxxxxxxx; CDT General developers list.
Subject: Re: [cdt-dev] CMainTab ui

 

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
Sent: Wednesday, October 22, 2014 3:57 PM
To: CDT General developers list.
Subject: [cdt-dev] CMainTab ui

 

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
and less confusing

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,
programmatic logic of enabling/disabling it will be supported)


Back to the top