Safe QML objects individual hash code handling with multiple QML component files

The individual hash code management is unclear at the moment for hierarchical QML component files.

With the component files, it is possible that there are safe QML objects with the same identification and hence same hash value counted from the identification.

When the hash code is used for identifying the safe QML object (e.g. sending the event, or the monitor is reporting errors), we are not exactly sure which particular safe QML object is the actual that is affected, if there are same hash codes.

We need to define the wanted behavior and have automated tests showing that the wanted behavior works. (automated tests can have relatively simple hierarchy, but extreme cases could be checked with automatically generated complex QML hierarchies with the Python scripts)

There are at least following things to consider:

• accidental similar names in a complex design
• reuse of the same component in the same design 
  • note the parsing if the reuse is not in a same hierarchy level
• hash values for the monitor (and debugging it)
• hash values in following cases (check if there is impact or not)
  • source image is changed in some state 
  • localization with multiple layouts
  • layout changes (e.g. cluster demo)
    • can there be same names and hash values with different layouts, or not?
    • If yes, do we assume (=mother of all fuck-ups) that the same identification always means the same safe QML object? What if there are same names used in different components by different authors and for clearly different safe QML types (and those are then mistakenly confused). Or is it keyboard external error? 
  • etc
• identification values in extreme cases
  • super long names, are there any limits
  • do we support other input than some specific Latin character set?
    • If someone is doing the software in Arabic or in Chinese
  • can there be numerals in the beginning, end, only numerals etc
  • what if the identification is left empty
  • what if the identification is only a white space, or multiple white spaces
  • will the QML parser detect some of these