Hi,

a customer found an issue in the System Profiler. He tried to set Event Filters for the log (before the log gets done) 
and decided to select Class Specific. By doing that, the IDE displays tabs for each class and there you can set Fast, 
Wide, Event Specific or Disable.

The customer set Control Events to Disable and then had issues opening the log file later. In my understanding, 'Control
 Events' are

1) not visible in the timeline, because they are actually *used* to coordinate the event generation (e.g. logging a 
ClockCycles wrap)

2) mandatory to be enabled, because without them, the System Profiler (and probably traceprinter) cannot completely 
interpret the kernel log.

Is this correct? If so, it should not be possible to manipulate the setting for Control Events at all, thus the 
corresponding tab should not be displayed. Shall I file a PR?


- Malte