feat(frontend/table): enable tag selection#180
Merged
CammilleCC merged 6 commits intomainfrom Feb 16, 2026
Merged
Conversation
This was referenced Feb 11, 2026
CammilleCC
force-pushed
the
feat/table-tag-selection
branch
from
d5f8931 to
2ca4993
Compare
CammilleCC
force-pushed
the
feat/table-tag-selection
branch
from
2ca4993 to
273d904
Compare
CammilleCC
changed the base branch from
feat/table-variable-visibility
to
chore/per-branch-gh-pages
CammilleCC
added a commit
that referenced
this pull request
Feb 13, 2026
This PR adds the following tags on the XPCS example data to help visualize #180. - Run details - Beam properties - XPCS
CammilleCC
added a commit
that referenced
this pull request
Feb 16, 2026
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
1 participant
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.
Second step after #179
We now expose the tag selection on the table as well, aiming to use tags as a filter on top of variable visibility. This is in line with the discussion earlier with Olly, with the current PyQt implementation generally preferred.
I have now added
useColumnVisibilityto derive the actual visible variables with this and variable visibility in mind. The interaction between the two could still be improved, in terms of the interface, which I plan to do so as a next step.chrome_vnodNwgrgV.mp4