| View Issue Details [ Jump to Notes ] | [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0006838 | IGSTK | IGSTK | public | 2008-04-17 10:53 | 2008-06-17 10:34 |
|
| Reporter | Matt Turek | |
| Assigned To | Matt Turek | |
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
|
| Summary | 0006838: Reorganize event hierarchy to allow for easier error handling. |
| Description | The current event hierarchy makes it difficult to do generalized error handling. There is no way to register for only error events or only error events pertaining to a specific subset of functionality.
This issue was raised during the IGSTK 2008 Strategic Planning meeting http://public.kitware.com/IGSTKWIKI/index.php/IGSTK_Strategic_Planning_2008 [^]
See February 25, Monday, 1:00 ~ 3:00, item 14.
The goal is to reorganize the IGSTKEvent hierarchy by inserting an IGSTKErrorEvent that will be the superclass of all IGSTK error events. In addition, error event classes will be inserted into the hierarchy to group related errors together. Some portions of IGSTK already have this hierarchy in place (e.g. TrackToolErrorEvent) but the design/implementation is not consistent across the toolkit.
The current and proposed event hierarchy may be found under the Event Hierarchy Survey2 section at:
http://public.kitware.com/IGSTKWIKI/index.php/Error_Event_Management#Event_Hierarchy_Survey2 [^]
|
| Tags | No tags attached. |
|
| Attached Files |  current.pdf [^] (20,585 bytes) 2008-04-17 11:11
proposed.pdf [^] (21,881 bytes) 2008-04-17 11:11 |
|