Hi @Johan Söderlind Åström,
it's more clean to do this kind of check somewhere else than in the view, which is mostly tasked with just presenting values. If you review the MVP structure of a TouchGFX application you could say that each View/Presenter is a state in itself in a statemachine where the presenter determines what to display and when. You could also say that model.cpp would get really bloated with a lot of checking of different values.
If you don't want to do this kind of check in the model you could create some more "Models" that handle specific areas of the domain. The far easiest is just to signal active presenters that some huge struct of data has changed, but you _may_ be left with less transparent code in the end. It's difficult to say. On the other hand, your modelListener interface will be simpler and you know that you should look for processing of "temperature" data in the "TemperaturePresenter" - Maybe. You see my point? Depending on your project, things can be cleaner or more messy.
If you want to go your current route with a single signal for all data, you should probably do your checks in the presenter, at least.
