4 ms·
Are the 'safety critical' UI components rendered any differently to the non-critical ones? From reading the related blog posts, I understand that they are gener
by joosters 8y ago
Are the 'safety critical' UI components rendered any differently to the non-critical ones? From reading the related blog posts, I understand that they are generated in a separate process, but asides from that detail, are they any more reliable?
Or to put it another way, if we an pick some UI components and marking them as safety critical' somehow improves their reliability, why would you not mark everything as safety critical?
Does the safety factor decrease as more and more components enter the safety critical section? Why not subdivide the UI into more than just one 'critical' process and one 'non-critical' process, e.g. perhaps a light-weight process per component?
- freedomben 8y agoThe article links to http://blog.qt.io/blog/category/functionalsafety/ http://blog.qt.io/blog/category/functionalsafety/ which has a lot more details. The short answer tho, is that "the tooling separates out the safety-critical elements for execution by the Qt Quick Renderer run-time."
- gmueckl 8y agoI talked to one of the devs a whule ago: the safety critical part of the display is rendered by a completely separate renderer which is kept as simple as possible. Most of the application specific code for it is generated automatically and a lot of the typical dynamic behaviour (dynamic memory allocation etc.) is strictly forbidden so that the result follows the requirements of safety standards.