<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Okay. Let my try to understand what is happening here.<div class="mb_sig"></div>
<div><br></div><div>Platform: LinuxARMv8</div><div><br></div><div>1. Resize window to ??? then save-and-quit.</div><div>2. Open on a 1920 by 1080 screen but window is smaller than ???.</div><div>3. Open on a 1920 by 1440 screen and window is exactly ???.</div><div><br></div><div>So, what is ??? in this scenario? :-)</div><div><br></div><div>And what are the results of...</div><div><br></div><div>Display platformScaleFactor.</div><div>Display uiScaleFactor.<br></div><div><br></div><div>Best,</div><div>Marcel</div><blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 30.05.2022 19:02:24 schrieb tim Rowledge <tim@rowledge.org>:</p><div style="font-family:Arial,Helvetica,sans-serif">Sorry if I wasn't clear - it's the *host* window size that is messed up for me.<br><br>> On 2022-05-30, at 2:40 AM, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:<br>> <br>> Hi Tim --<br>> <br>> Are you referring to the host-window size or the system-window size? I think you mean the latter. Whether or not the scale factor is involved, you can check by looking at what is selected in "Extras > Scale Factor" menu.<br>> <br>> I am not sure that I really understand what you mean. However, there are two hard-coded numbers in RealEstateAgent class >> #strictlyStaggeredInitialFrameFor:... which we did not adjust to the scale factor.<br>> <br>> ...<br>> "Number to be staggered at each corner (less on small screens)"<br>> maxLevel := allowedArea area > 300000 ifTrue: [3] ifFalse: [2].<br>> "Amount by which to stagger (less on small screens)"<br>> grid := allowedArea area > 500000 ifTrue: [40] ifFalse: [20].<br>> ...<br>> <br>> Would you apply a "* self scaleFactor" to those areas and see if the problem gets fixed? :-) Maybe also the grid.<br>> <br>> ---<br>> <br>> This is most likely not a VM issue but related to a feature in newer VMs. It might be that a newer VM will actually deliver that platformScaleFactor which will then set the image-side uiScaleFactor which will then modify the "RealEstateAgent scaleFactor" which will then result in bigger default-window areas and thus hit those magic boundaries. Not sure.<br>> <br>> Best,<br>> Marcel<br>>> Am 29.05.2022 20:54:38 schrieb tim Rowledge <tim@rowledge.org>:<br>>> <br>>> I'm just trying the latest release VM (ARMv8 on a Pi in this case) and it seems to be doing Odd Things with the window size.<br>>> <br>>> The same image on two different Pis opens with different window sizes. One Pi has a 1920@180 screen and the initial window is notably smaller than what it was when I saved the image, the other has a 1920@1440 screen and the initial window size is what I set. That size is not larger than the 1920@1080 screen, by the way. To the best of my recollection this is new (mis)behaviour.<br>>> <br>>> We've always done some startup checks in the VM to fit the window within the available display limits but I don't remember previously over-riding the requested size this aggressively. Has anyone changed this code recently? Or is this a side effect of recent scale factor stuff? I can't spot any suspicious code in the image right now.<br>>> <br>>> tim<br>>> --<br>>> tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim<br>>> A misplaced modifier walks into a bar owned a man with a glass eye named Ralph<br>>> <br>>> <br>> <br><br><br>tim<br>--<br>tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim<br>Useful random insult:- Always responds to "Make Money Fast" postings on the Net.<br><br><br><br></tim@rowledge.org></marcel.taeumel@hpi.de></div></blockquote></div>