Qt Safe Renderer Feature Requests

This is a collection of unsorted requirements that need to be analysed validated before committing to the next version of the product.
QTPM-620 is now the mast copy of these requirements.

Icon Browser

See QTAUTO-513

The current prototype puts all elements of type Picture into the Safe Render category. With over 7000 icons there is a possibility that not every Picture element in a screen should be marked for safe rendering. Would it make more sense to have a property that marks the item?

7000 icons is too many for someone to find one easily in the Icon Browser of QtCreator. Possibilities are search but that isn't good for browsing. Other option is to group by category since they already have categories. As icons have multiple categories this means they could appear in multiple places.

Is there a way for customers to add their own custom icons? How do they do this? Are any special tools required?

Notes from a customer (VW Futurelab) meeting

• Icons can move, for example when the different cluster views are presented and the icons are then in different positions. They would then be animated as they move to new position. Another scenario is that warning icons are a centered list and as new icons are lit they re-arrange. But really the requirement is that the designer needs the freedom to do anything.
• Icons can also be scaled in this scenario but we agreed that this requires bitmaps at different scales as drawing on the fly is not possible (but how complex is the rendering from the vector icon?)
• Stick with option 1; saferenderer always draws on the top. The alternative is very difficult, Chris couldn’t see an easy way to do it.
• We need an intra-VM communication medium.
• Treat positioning parameters as insecure and test that they are correct and if something is really wrong have a panic UI which says to pull off. Test for off screen and colliding icons. Assumption is that everything should be tested before production so if such an error condition is detected then something really bad has happened.
• Text support needed. Text as bitmap is ok. Create during the build phase. Requires dynamic positioning just like the icons. Localization requires bitmaps for each language. How to load at run-time? This means that language needs to be an input to the safe renderer.
• Not clear: what is the background for icon? Done at design time but then that information also needs to go to the safe renderer.

ISO2575 Investigation

The new ISO2575 standard compiles over 350 symbols (i.e. conventional signs) for use on controls, indicators and tell-tales. It also provides guidance on the proper colours of optical tell-tales, which inform the driver of either correct operation or malfunctioning of the related devices.

We need to purchase this specification and see which ones are in the ISO7000 list and which are not.

Other Items to consider

• Some customers have discussed the possibility of safe touch areas so that some buttons, such as hazard lights, can be moved to the touch screen. There is low expectation that this will become a firm request, documenting that it has been mentioned.

Qt Safe Renderer futures: Denso via Johannes, 5th July 2017

• They would like to have fade-in/out effect in the safety critical side
• Their customers are also requesting gear shift indicator to be safety critical and would like to have a slide animation in it
• Needles to be implemented in safe renderer (already 2nd time this is requested by Japanese Tier1s)
• They would like to use Qt Safe renderer not only for safety critical UI, but also to implement fast starting minimal UI at cold boot.
• Safe renderer additional features - PRDN, images to show needles, check for app background blending with icon color