So imagine you have 

```
switch(systemAlarmsData.ConfigError) {
case SystemAlarms::CONFIGERROR_STABILIZATION)
  alarmDescription.setFileName(QString(":/systemhealth/html/SystemConfiguration-Error.0.html")
  break;
case SystemAlarms::CONFIGERROR_MULTIROTOR)
  alarmDescription.setFileName(QString(":/systemhealth/html/SystemConfiguration-Error.1.html")
  break;
}
```
The hardwiring is still present, but since it's no longer directly linked to the enum's magic value the code is robust in the case that the UAVO value changes.