This project is mirrored from https://github.com/mantidproject/mantid.git.
Pull mirroring updated .
- 17 Sep, 2021 2 commits
-
-
- 10 Sep, 2021 5 commits
-
-
Zhou, Wenduo authored
-
Zhou, Wenduo authored
-
Zhou, Wenduo authored
-
Zhou, Wenduo authored
-
Zhou, Wenduo authored
-
- 17 Aug, 2021 2 commits
-
-
- 10 Aug, 2021 1 commit
-
-
Add parent to QMenu objects so they get deleted when the parent matrix workspace view gets deleted
-
- 29 Jul, 2021 2 commits
-
-
This greatly simplifies the understanding of the files themselves as they then simply match more standard Python projects. The driving CMake code then simply makes use of them as a user would.
-
- easy_install is no longer distributed - we pass in the Qt install root rather than guessing it We also pin the pip installed packages to those that were used to build the package rather than maintaining a separate list of version numbers. This particularly ensures that the versions of numpy match appropriately and will ensure more reproducibility in the package
-
- 19 Jul, 2021 1 commit
-
-
Kendrick, Coleman authored
-
- 16 Jul, 2021 1 commit
-
-
Kendrick, Coleman authored
-
- 15 Jul, 2021 1 commit
-
-
Peterson, Peter authored
These are minor issues having to do with types (yes, I know it is python) and leaving dangling file references.
-
- 07 Jul, 2021 4 commits
-
-
Peterson, Peter authored
-
Peterson, Peter authored
-
These classes cannot be marked final as a Nice/Strict mock inherits from the original mock class, rather than holding it as a member. This means that we need to mark the mocks with a virtual d'tor as we (unintentionally) have them as part of an inheritance chain
-
Correctly add a virtual dtor to IAlgorithmProgressWidget
-
- 02 Jun, 2021 2 commits
-
-
Samuel Jones authored
-
Samuel Jones authored
-
- 01 Jun, 2021 5 commits
-
-
Whitfield, Ross authored
* type hints and actions package Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * forward declarations to prevent import loops Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * forward declarations to prevent import loops Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * Add buttons and combo box * Update function name * subscribing the presenter to the viewer Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * Modify grid layout * Include correct import * Add actions.ui file * Tying the PeaksActionModel to the presenter Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * Instantiating the peak actions Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * group box in ui file Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * append/remove PeaksWorkspace from the view Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * resolve circular imports Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * lazy connections between vier and presenter Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * getattr should've been hasattr Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * getattr should've been hasattr Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * route signals only when presenter is not None Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * Hack to get everything showing, need to fix PeakAction size policy * Get remove_peaks working * Add a peak to the workspace * Ugly but have peak adding working * Add minimum size to PeakActionsView * Move coordinate transform to sliceview presenter * Move add_peak from PeakAction model to PeaksViewer model * Trigger ADS update when adding peaks from python * Check one button at a time * Disable pan and zoom while adding peaks * Add minimum width for actions widget * Force draw after workspace replaced * Deactivate peak adding if pan or zoom selected * Remove handle PeakActionsPresenter from PeaksViewerCollectionView Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * rename peaks_actions_view property Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * Revert "rename peaks_actions_view property" This reverts commit 0b59766b. * Revert "Remove handle PeakActionsPresenter from PeaksViewerCollectionView" This reverts commit c3eeb15b . * PeakActionsPresenter not used in PeaksViewerCollectionView Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * Remove actions presenter and view Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * move actions/view.py to peaksviewers/ Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * Cleanup peak adding * Change 'button_press_event' connection * Fix button selections * Add tests for adding peaks in peaksviewer * Add test for sliceviewer.presenter/peak_add_delete * peak deletion deletes peak closest to input position Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * Unify deleting/adding peaks Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * test delete peaks Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * Don't need to include frame from sliceviewer, PeaksViewer knows this * Change SliceViewer.peak_add_delete to add_delete_peak to make it the same as PeaksViewerCollectionPresenter Also simplify PeaksViewerModel.delete_peak * Add peaksviewer/sliceviewer integration test for add/remove peaks * send AfterReplaceNotification after removal of a peak Signed-off-by:
Jose Borreguero <borreguero@gmail.com> * Fix coordinate transform * Make PeaksViewerModel.delete_peak faster * Fix test_peak_add_delete_event * Fix workspace ordering with multiple peaks workspaces And cleanup some unused methods. * Add test for PeakActionView.set_peaksworkspace * Update docs * Change replace/rename handle to keep same position * Adjust test for changes to replace/rename handle * Set visibility specs * Update docs * Forgot to add new image * Fix two issue with peak overlay display, Should be checking all workspaces instead of just newly added workspaces. Deactivate peak adding/removing when peak overlay is closed Co-authored-by:
Jose Borreguero <borreguero@gmail.com> Co-authored-by:
Jenna Delozier <jennakate998@gmail.com> Co-authored-by:
Jenna DeLozier <52164248+jenest@users.noreply.github.com>
-
Samuel Jones authored
-
Daniel Murphy authored
Put this workaround in common function in mantidqt.utils
-
Daniel Murphy authored
-
Samuel Jones authored
-
- 27 May, 2021 1 commit
-
-
Gigg, Martyn Anthony authored
If we cannot generate a valid completion list then we should just stay silent and not show errors
-
- 26 May, 2021 3 commits
-
-
Danny Hindson authored
When viewing instruments that have banks that are width "one detector" in x or y or z, the instrument viewer was giving a warning about "failed to build unwrapped surface" when you viewed in one of the cylindrical projections. Remove the warning and also the code to assign values to u_min and u_max shortly after. The pre-existing values of 0 and 0 are fine for these values which are in radians Also include some line length changes that come from the latest clang format version
-
Samuel Jones authored
* Implement threading similar to project recovery for memory widget * Improve mainwindow closeEvent and clean up test threads properly * Remove old test in Cmake * Ensure updates are cancelled and not restarted * Make the memorypresenter more generic * increase stability of tests * Implement review feedback * Remove unstable tests * Reintroduce now stable test and utilise separate threaded methods * Stability improvement * Further test stability improvements * Use a more specific time to wait to ensure that the value is set * Memory presenter test stability
-
Robert Applin authored
-
- 25 May, 2021 4 commits
-
-
Robert Applin authored
-
Robert Applin authored
-
Robert Applin authored
-
Robert Applin authored
-
- 24 May, 2021 4 commits
-
-
Matt Cumber authored
-
Srikanth Ravipati authored
-
Srikanth Ravipati authored
-
Srikanth Ravipati authored
-
- 21 May, 2021 2 commits
-
-
Dominik Arominski authored
-
Dominik Arominski authored
-