feat: add 2d ConfigPresetsTable#449
Merged
tlambert03 merged 10 commits intopymmcore-plus:mainfrom Jul 1, 2025
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #449 +/- ##
==========================================
+ Coverage 87.19% 87.39% +0.19%
==========================================
Files 99 100 +1
Lines 10933 11122 +189
==========================================
+ Hits 9533 9720 +187
- Misses 1400 1402 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
continuing with views onto the new model from #447, this adds a 2D Config Table widget.
It represents a single Configuration group with presets as Columns (or rows), and the union of all dev-prop pairs as rows.
It's best suited for groups that share the same combo of device properties across all presets... but works either way. A missing Dev-Prop in a given preset will show as an empty cell
Double clicking on the cell reveals a property-value-specific editor widget
closes #320