Skip to content

Comments

Draw detectors as their shapes in new Instrument View#40850

Draft
jclarkeSTFC wants to merge 11 commits intomantidproject:mainfrom
jclarkeSTFC:40311_draw_detectors_actual_shapes
Draft

Draw detectors as their shapes in new Instrument View#40850
jclarkeSTFC wants to merge 11 commits intomantidproject:mainfrom
jclarkeSTFC:40311_draw_detectors_actual_shapes

Conversation

@jclarkeSTFC
Copy link
Contributor

Closes #40311.

To test:


Reviewer

Your comments will be used as part of the gatekeeper process. Comment clearly on what you have checked and tested during your review. Provide an audit trail for any changes requested.

As per the review guidelines:

  • Is the code of an acceptable quality? (Code standards/GUI standards)
  • Has a thorough functional test been performed? Do the changes handle unexpected input/situations?
  • Are appropriately scoped unit and/or system tests provided?
  • Do the release notes conform to the guidelines and describe the changes appropriately?
  • Has the relevant (user and developer) documentation been added/updated?
  • If the PR author isn’t in the mantid-developers or mantid-contributors teams, add a review comment rerun ci to authorize/rerun the CI

Gatekeeper

As per the gatekeeping guidelines:

  • Has a thorough first line review been conducted, including functional testing?
  • At a high-level, is the code quality sufficient?
  • Are the base, milestone and labels correct?

This is slower than drawing them as points, but is a more accurate
representation of the instrument. Both points and shapes drawing
classes derive from a common base class, to ease switching in the
presenter.
When drawing as shapes, and a detector is picked, it will be
highlighted by drawing a wireframe outline around it.  This is
implemented by maintaining a separate mesh containing just the
highlighted detector, which is drawn on top of the main mesh.
When the highlighted detector changes, we update the vertices of
this mesh to match the newly highlighted detector.
@jclarkeSTFC jclarkeSTFC added this to the Release 6.16 milestone Feb 9, 2026
@jclarkeSTFC jclarkeSTFC added the Epic Used for issues and PRs that are managed under the ISIS Epic Workstream label Feb 9, 2026
@github-actions github-actions bot added the Has Conflicts Used by the bot to label pull requests that have conflicts label Feb 9, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

👋 Hi, @jclarkeSTFC,

Conflicts have been detected against the base branch. Please rebase your branch against the base branch.

@jclarkeSTFC jclarkeSTFC removed the Has Conflicts Used by the bot to label pull requests that have conflicts label Feb 9, 2026
When picking points the detectors are hightlighted in orange, so let's
keep consistent behaviour. I also removed some unused arguments in some
renderer methods.
Copy link
Contributor Author

@jclarkeSTFC jclarkeSTFC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rerun ci

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Epic Used for issues and PRs that are managed under the ISIS Epic Workstream

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Draw detectors as their actual shape

1 participant