Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
09/11/13 16:51:06 (11 years ago)
- Author:
-
mtbcarroll
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
initial
|
v1
|
|
| 1 | | So, what's happening here is that when a ROI is deleted, `MeasurementViewerModel.onROIDeleted` gets called twice; each time it sets the model state to `READY`. The first call is caused when the save button is pressed by `MeasurementViewerComponent.saveROIToServer` dispatching a `DeleteActivity` to the `MeasurementAgent`; the second follows in the event dispatch thread as `DataObjectRemover.update` and goes on to call `DeleteActivity.endActivity` which again reaches `onROIDeleted` setting the state to `READY`. |
| | 1 | So, what's happening here is that when a ROI is deleted, `MeasurementViewerModel.onROIDeleted` gets called twice; each time it sets the model state to `READY`. The first call is caused when the save button is pressed by `MeasurementViewerComponent.saveROIToServer` dispatching a `DeleteActivity` to the `MeasurementAgent`; the second follows in the event dispatch thread as `DataObjectRemover.update` goes on to call `DeleteActivity.endActivity` which again reaches `onROIDeleted` setting the state to `READY`. |
| 2 | 2 | |
| 3 | 3 | `MeasurementViewerModel.fireLoadROIServerOrClient` gets called once, in the event dispatch thread, effectively by `ROISaver.handleResult` receiving ROIs as the result of a `DSCallOutcomeEvent`, and it sets the state to `LOADING_ROI`. |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.45036 sec.)
