Mike Behm came up with these good suggestions: It would seem to be pretty time-consuming to click on all of the custom observer types to determine what each does. Would it be desirable to list the observers by their configured actions? Something like: Observers Stop Resume Source Code Print State ---------------------------------------------------------------------------- Exec Observers Special Observer x x Also, in the Actions view is there any advantage to listing Action Points? Would it be enough to list the available actions (Stop, Resume, Source Code, and Print State) and allow the user to move these to "Current Actions" as required?
I like the suggestion from Mike Behm... and the diagram certanly seems better than what i have attempted to do with the treeview on the left hand side. ActionPoints, like FilterPoints are nessesary, since they represent the argument that is sent to an action... for example stop action should be applied to wich thread ? which actionpoint it is added to determines that. Clearly the GUI is not doing a good job demonstrating that. I am open to suggestions on possible improvements.
A suggestion from Mike Bhem was to calculate all the permutations of actions and action points and just display that to the use in one list. This will be addressed in new observers dialog
This is done. The user only has to make one choise when adding an action to an observer.