should not show its own events and avoid at least part of its interface
@sthibaul
Submitted by Samuel Thibault Link to original bug (#794086)
Description
Created attachment 369346 screenshot
Hello,
Accerciser is accessible, which is a good thing, but leads to unbound loops.
For instance, if one browses accerciser's tree of widgets in the tree table up to the tree table (as shown in attachment), accerciser loops adding elements to the tree table. There could be a matching rule which prevents from opening that exact element of the tree.
Similarly, if accerciser events get included in the event monitor, we keep getting events telling that the event monitor got modified. There could also be a matching rule which avoids showing events about the event monitor.
Samuel