Adding Display ratio

[adragnevVW]

No description provided.

[adragnevVW]

This is a refresh of #108

[AndriiVoitenko]

But I still have the same doubts as in this comment: #108 (comment)

[adragnevVW]

Hi @ILane-VW & @AndriiVoitenko,
I've updated the way we export display ratios by adding width (unsigned int), height (unsigned int), and aspect ratio (double).
This change allows us to export generic display ratios in a more precise and flexible way. Storing width and height preserves the exact ratio (like 3:4 or 16:9), while the double aspect ratio provides a ready-to-use numeric value for calculations and comparisons. Using unsigned integers ensures no negative values.

[AndriiVoitenko]

Hi @adragnevVW,

and what about synchronization? I mean in the end of the day display has only one aspect ration. And currently user can specify width 4, height 3 and ratio 1,7777, mean and depending on which API he will call, the result will be different for the same object.

Therefore it is not a good idea to duplicate data. Sure you can provide 2 API, but internally store only one set of data, for example as we discussed on Friday: store 2 integers and by requesting of double calculate it.

Beside that, we still do not have it in a specification, so you should not merge it to the library until new version of specification posted + IsCurved new property, right? This one should be also addressed by specification group.

[AndriiVoitenko]

see on conversation page