Community
Participate
Working Groups
More granular verification hooks required. AGR gives users the ability to also insert verification hooks based on a view, editor, or a shell. Often, testers are interested in single widgets and need to search for the widget in the view, editor, or shell. When the user selects a widget in the UI to insert a verification hook, they should determine what level of the widget's ancestry they wanted passed into the verification hook method.
Enhancement request.
Correcting priority since not a 4.5 candidate enhancement (see http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html).
In TPTP 4.5, the AGR was moved from a Technology Preview component to an As-Is component. As-Is components are primarily provided for prior users but imply no support (for example, defects, news group, and mailing lists) or commitment to triage or resolve opened defects. For this defect to be considered, please re-open with an attached patch including code to resolve the symptom and test cases to test the fix.
Closing.
In the patch (revision of AGR) I uploaded to bug #133099 this issue is resolved by introducing a new "extended scope" mode to verification hook insertion, which will add one/two additional parameters to the verification hook method to pass in the selected widget and (optional) a nested (non-widget) object on it. The Draw2d extension of AGR proposed by the patch in bug #133099 demonstrates this by showing how a verification hook for IFigures located on a FigureCanvas widget is added in "extended scope" mode (the respective editor, the figure canvas and the figure are then passed into the hook method as parameters).
