Dec 09 and Dec 11, 2015
John Clyne, alan, scott
Alan completed error handling changes discussed last week and we reviewed the new GUI user notification popups.
We had further discussion on how to handle recoverable errors within the GUI when the error may have occurred within a library and return an error code. Two options were suggested:
Further discussion on the best choice is required. John pointed out that whatever method we choose to propagate the information back to the GUI we need to not make assumptions about how other applications (e.g. command line utilities, scripting interface) will want to make use of the error handling mechanisms provided. In particular, error reporting needs to be disabled (via MyBase::EnableErrMsg()) if a class method is able to recover from a "fatal" error. Otherwise, any error conditions will result in error callbacks or messages to stderr, etc.
WE also reviewed the GUI
Item | Description | Lead |
---|---|---|
1 | Design review for animation and key framing | John |
2 | Design review for region tab | John |
3 | Further discussion on error handling in GUI | John |
4 | Revisit the subtab scheme and consider Scott's suggestion of having "basic" and "advanced" tabs | Scott |