question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Remove the extra drop down for configurePresets

See original GitHub issue

Brief Issue Summary

  1. the target selection thing is missing (not discussed here. see #1872)
  2. Selecting 3 presets (config, build, test) takes a lot of status bar space

Expected:

  1. target should be shown (like in non-preset-mode) (not discussed here. see #1872)
  2. they should be combined into one button

Suggestion:

<TOOLS> Presets | [Target] | <GEAR> Build | <BUG> | <PLAY> | <FLASK> Run Ctest

Note: <FOO> are Icons, | seprarate clickable stuff

Presets should run > Select configure preset, Select build preset and Select test preset at once, (current one should be preselected) and not show the names in statusbar. [Target] should be used for build and launch target

I know, some of this can be configured via cmake.statusbar.advanced, but some can not.

Another bonus would be to check if there is a config, build and test preset with the same name. Then use those on selection

> Select Presets
> Chose configuration presets
> The same preset name exist for build and test. Use those (**Yes** No)
Yes -> exit
No ->
> Chose build preset
> Chose test preset

Platform and Versions

  • Operating System: Windows
  • CMake Version: 3.20.4
  • VSCode Version: 1.57
  • CMake Tools Extension Version: 1.7.2
  • Compiler/Toolchain: irrelevant

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:1
  • Comments:9 (8 by maintainers)

github_iconTop GitHub Comments

2reactions
bobbrowcommented, Jun 23, 2021

For the first issue, there is more discussion here: #1872 We will use this issue to track the second request.

1reaction
tntfbcommented, Aug 24, 2021

Actually, I don’t see a reason why the Active Configuration Preset should even be in the statusbar. The Build Preset already carries its selected configuration preset, as per the cmake-presets documentation:

configurePreset

An optional string specifying the name of a configure preset to associate with this build preset. If configurePreset is not specified, it must be inherited from the inherits preset (unless this preset is hidden). …

That CMake Tools is forcing a redundant selection of a configuration preset before the Build or Test preset cab be selected should be marked as a bug. The Configuration preset should be removed from the statusbar and the actual configuration should follow the selected Build or Test preset automatically.

Read more comments on GitHub >

github_iconTop Results From Across the Web

CmakePresets: Selecting of build targets seems not to be ...
The selected target is passed down to CMake when running the ${command:cmake. ... Remove the extra drop down for configurePresets #1945.
Read more >
Add or remove items from a drop-down list - Microsoft Support
Edit a drop-down list that's based on an Excel Table · To add an item, go to the end of the list and...
Read more >
Remove a drop-down list - Microsoft Support
To remove a drop-down list, click the cell with the list, then click Data > Data Validation, and then on the Settings tab,...
Read more >
How to Edit a Drop-Down List in Excel - YouTube
Learn how to edit a drop - down list in Excel - quick and easy. In the previous excel tutorial, we went through...
Read more >
Configure output presets for conditional content
The tag is removed from the Condition Tags panel and appears in the ... From the Dynamic Content Filter drop-down list, select a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found