Bug 546523 - Launchbar sets active config to default after a Run or Debug build
Summary: Launchbar sets active config to default after a Run or Debug build
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: launchbar (show other bugs)
Version: 9.7.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-17 11:36 EDT by Jeff Johnston CLA
Modified: 2020-09-04 15:22 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Johnston CLA 2019-04-17 11:36:04 EDT
If a target such as a Container target is selected and either the Run or Debug buttons of the launchbar are pressed, the build and run/debug work as expected, however, after the run/debug, the active target is set to default even though the pull-down menu shows different.  This affects the indexer and clicking on the outline view will result in bringing up the local headers.

The only way to change back is to change the target to something else and then back again as selecting the same target won't cause the target change to occur.
Comment 1 Doug Schaefer CLA 2019-04-17 14:10:24 EDT
By default, sounds like you mean the config used by the indexer (not sure that qualifies it as a "default" but I get what you mean).

In the managed build, we had a project setting to pick the build configuration to use for indexing. It would make sense to have something similar for Core build.
Comment 2 Doug Schaefer CLA 2019-04-17 14:22:10 EDT
BTW, a similar issue I run into is what build config the Build Project menu item runs. In theory it's the last one set by the Launch Bar. Would be good to make that explicit as well.