Skip to content

Conversation

@adragnevVW
Copy link
Collaborator

Adding parameters for Display geometry object

Issue:
The Display object was not containing the Aspect Ratio of the screen.

@adragnevVW adragnevVW self-assigned this Jul 28, 2025
@adragnevVW adragnevVW added the Waiting for Review PULLREQUEST is waiting for review label Jul 28, 2025
@AndriiVoitenko
Copy link
Collaborator

Have I missed something? According to specification there is no AspectRatio xml attribute in Geometry type Display.

image

@adragnevVW
Copy link
Collaborator Author

Hi @AndriiVoitenko,
I know that it is not in the spec, but I think we need to consider adding it, because this one of the main parameters of displays.

@adragnevVW
Copy link
Collaborator Author

Is there any other way how we can export the ratio of the Screens?

@AndriiVoitenko
Copy link
Collaborator

AndriiVoitenko commented Jul 28, 2025

You are right, and there was already discussion about ration aspec. Nevertheless I am not sure about type of this value. Yes string can handle everything, but those everything will cause problems by controller and visualizer, maybe enum or at least some predefined value will be more suitable for it. Next question would be is it a mandatory xml attribute or optional one. In your current implementation it is mandatory one (as you do not has HasRatioAspec function) and empty as default value. And if it is, as you say "main parameters of display" then it should have suitable default value, otherwise it would not help you to visualize it.

Long story short: from my point of view, we need clarification on it before implement it in the library.

@adragnevVW
Copy link
Collaborator Author

@AndriiVoitenko I think you are right, we need to discuss it more what we need to add about the displays. Also my opinion is that it need to me mandatory, because of that every screen have specific ratio.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Waiting for Review PULLREQUEST is waiting for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants