<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p><span style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt">Hi Tobias,</span><br>
</p>
<p><span style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt"><br>
</span></p>
<p><span style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt"></p>
<div>> > For the first step, we could start by asking the user whether they would like to change the font size (#changeFontSize:) when a new scale factor is detected, couldn't we?</div>
<div>> </div>
<div>> No, that ought to be automatic;</div>
<div><br>
</div>
</span>
<p></p>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif,EmojiFont,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols">
<div name="x_divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div>
<div class="x__rp_T4" id="x_Item.MessagePartBody">Personally, I'd prefer a preference for this. ;-) My Windows system often changes its DPI value multiple times a day and #changeFontSize: has a big impact on your image as it replaces the UI theme (for example,
all windows are resized and repositioned, custom theme adjustments are lost, <a href="http://forum.world.st/BUG-Updating-TheWorldMainDockingBar-leaves-dangling-results-widgets-td5110474.html" class="x_OWAAutoLink">
the search bar</a> is emptied, and the history of workspaces is cleared). Also, it's an expensive operation that can slow my system down for ca. 10 seconds per open image. I would only change the font size if I need it just at the moment (I always use to keep
open several images even if I do not use all of them frequently).</div>
<div class="x__rp_T4" id="x_Item.MessagePartBody"><br>
</div>
<div class="x__rp_T4" id="x_Item.MessagePartBody">Best,</div>
<div class="x__rp_T4" id="x_Item.MessagePartBody">Christoph</div>
</div>
<div><font size="2" color="#808080"></font></div>
</div>
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Tobias Pape <Das.Linux@gmx.de><br>
<b>Gesendet:</b> Dienstag, 29. September 2020 10:28:01<br>
<b>An:</b> The general-purpose Squeak developers list<br>
<b>Betreff:</b> Re: [squeak-dev] highdpi testing</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi<br>
> On 25.09.2020, at 21:43, Thiede, Christoph <Christoph.Thiede@student.hpi.uni-potsdam.de> wrote:<br>
> <br>
> Hi Tobias,<br>
> <br>
> sorry I did not answer earlier! This approach looks better for me, however, the wheel is still not absolutely round:<br>
> <br>
> <br>
> (The shadows have a wrong position.)<br>
<br>
I know, I had a patch that worked in 2016, but things changed and I hand't had the time yet.<br>
<br>
> <br>
> For the first step, we could start by asking the user whether they would like to change the font size (#changeFontSize:) when a new scale factor is detected, couldn't we?<br>
<br>
No, that ought to be automatic;<br>
<br>
-t<br>
<br>
<br>
> <br>
> PS: @Tom:<br>
> > we try drawing things while we load things :)<br>
> For the case you did not already read it, I created a changeset that could solve this problem:
<a href="http://forum.world.st/Changeset-Eliminating-global-state-from-Morphic-tp5121690p5122464.html">
http://forum.world.st/Changeset-Eliminating-global-state-from-Morphic-tp5121690p5122464.html</a> It also allow me to file in the original DpiAware changeset.<br>
> <br>
> Best,<br>
> Christoph<br>
> Von: Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Tobias Pape <Das.Linux@gmx.de><br>
> Gesendet: Montag, 21. September 2020 15:50:30<br>
> An: The general-purpose Squeak developers list<br>
> Betreff: Re: [squeak-dev] highdpi testing<br>
> <br>
> Hi<br>
> <br>
> > On 19.09.2020, at 19:26, Thiede, Christoph <Christoph.Thiede@student.hpi.uni-potsdam.de> wrote:<br>
> > <br>
> > Hi,<br>
> > <br>
> > ah, I had assumed something like this, thanks for fixing, Tom! :-)<br>
> > <br>
> > #actualScreenScaleFactor is a very helpful tool, but I do not yet see the whole idea of the changeset.<br>
> > In what sense is this meant to be a complement of RealEstateAgent >> #scaleFactor or rather an orthogonal concept?<br>
> > After loading the changeset and resetting my UI theme, the background image of the world disappeared and all new windows are huge, but they still have a tiny font - am I supposed to set the #scaleFactor manually (to 12, in my example)?<br>
> > Where exactly can I see any components in the image that are upscaled by the new changeset?<br>
> > <br>
> <br>
> These do something.<br>
> Load in order:<br>
> <br>
> DpiAware-Kernel<br>
> DpiAware-Morpic <br>
> DpiAware-Display<br>
> <br>
> First two are harmless, third will do something.<br>
> If nothing changes, do <br>
> UserInterfaceTheme cleanUpAndReset.<br>
> <br>
> Issues ensue.<br>
> - Layouting borks. <br>
> The assert after the potential relayout <br>
> self assert: (self hasProperty: #doLayoutAgain) not <br>
> fails already in the docking bar…<br>
> - Fonts with UI-Themes do not work.<br>
> These are "Deep-referenced" to a pixel size (for Strike fonts) on creation, (so also during UserInterfaceTheme cleanUpAndReset).<br>
> However, when the scale factor changes, the pixel-sized fonts don't match the point sizes anymore…<br>
> This used to work pre-UI-Themes, as everyone requesting a Font did so by directly asking StrikeFont or TextStyle at the time the<br>
> Font was used. Hummm..<br>
> <br>
> Hope you enjoy.<br>
> -t<br>
<br>
<br>
<br>
</div>
</span></font>
</body>
</html>