rjwills28
commented
1 year ago Also noticed some bad scaling issues when refactoring cs-web-proto to use cs-web-lib. These OPIs look OK in the original so a change in cs-web-lib has caused the scaling to got awry in a few cases.
When trying to build a view that includes multiple embedded display or an embedded display and another elements (for example a webcam) the auto-scaling of the embeddedDisplay does not work correctly. This is because an Absolute position is used to define the location of the embeddedDisplay and this does not take up the whole of the browser display window. It means that you end up cutting off parts of the embeddedDisplay - example below. The amount visible depends on the size of the browser window hence suggestion that the scaling is not working properly.
I think the issue is that the previous scaling we implemented was based on the browser window size and does not take into account this case where there is a position allocated for the embeddedDisplay. This needs fixing the cs-web-lib.