[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: Review Request 122673: Make Svg, FrameSvg work qith QT_DEVICE_PIXELRATIO
From: "David Edmundson" <david () davidedmundson ! co ! uk>
Date: 2015-02-28 13:20:49
Message-ID: 20150228132049.12883.69137 () probe ! kde ! org
[Download RAW message or body]
--===============0872269998654100794==
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
> On Feb. 24, 2015, 11:52 a.m., Kai Uwe Broulik wrote:
> > src/declarativeimports/core/framesvgitem.cpp, line 495
> > <https://git.reviewboard.kde.org/r/122673/diff/1/?file=350723#file350723line495>
> >
> > Doesn't QWindow have a devicePixelRatio()? That way we could, one day, have \
> > separate scaling per monitor.
>
> Marco Martin wrote:
> yep, should eventually use that (tough i'm not sure yet) i should really find a way \
> to have one units instance per screen (or qwindow) instead per qqmlengine, that's \
> not going to be super easy compared how is done now
> Xuetian Weng wrote:
> What would be the qApp->devicePixelRatio() value if QT_DEVICE_PIXEL_RATIO set to \
> auto ? ...
> David Edmundson wrote:
> it's automatically set to 1.0 or 2.0 depending on your screen
I realised now I didn't read your question properly.
It's the DPI of the highest screen.
Rationale being if you supply a high DPI pixmap to a paintdevice with a \
devicePixelRatio of 1, then nothing bad will happen. It will just be implicitly \
scaled down.
- David
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122673/#review76547
-----------------------------------------------------------
On Feb. 22, 2015, 1:39 p.m., Marco Martin wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/122673/
> -----------------------------------------------------------
>
> (Updated Feb. 22, 2015, 1:39 p.m.)
>
>
> Review request for Plasma.
>
>
> Repository: plasma-framework
>
>
> Description
> -------
>
> (still in progress but here for feedback)
> when QT_DEVICE_PIXELRATIO is something different from 1, the pixmaps generated by \
> Svg will be scaled up to give a proper texture.
> This is complementary but not replacing our current approach:
> the pixelratio that can be accessed by units is now in relation to the qt pixel \
> ratio, spacings are also adjusted accordingly (therefore, spaces and sizes won't \
> need an integer value like pixelratio)
> svg introduces also a scaleFactor property (that is pretty much like its old \
> pixelRatio) basically, scalefactor, will scale both the textures *and* all the \
> reported sizes, (old method) pixelratio just scales textures without altering \
> measures (like qt pixelratio likes) they are now both used and combined, so a) we \
> can have this working before supporting officially qt pixelratio when will be good \
> enough but b) keeping the old mwthod working for the time being c) by using both at \
> the sae time we can at least scale sizes of values != from integers, for screens \
> that are too dense for 1 and not enough for 2
>
> Diffs
> -----
>
> src/declarativeimports/core/framesvgitem.cpp dae8a4f
> src/declarativeimports/core/svgitem.cpp 570c1c3
> src/declarativeimports/core/units.h 6c038ba
> src/declarativeimports/core/units.cpp a740145
> src/plasma/private/svg_p.h a31d0ac
> src/plasma/svg.h 0bcbd7a
> src/plasma/svg.cpp 0a0db5e
>
> Diff: https://git.reviewboard.kde.org/r/122673/diff/
>
>
> Testing
> -------
>
>
> Thanks,
>
> Marco Martin
>
>
--===============0872269998654100794==
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit
<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="12" style="border: 1px #c9c399 \
solid; border-radius: 6px; -moz-border-radius: 6px; -webkit-border-radius: 6px;"> \
<tr> <td>
This is an automatically generated e-mail. To reply, visit:
<a href="https://git.reviewboard.kde.org/r/122673/">https://git.reviewboard.kde.org/r/122673/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <p style="margin-top: 0;">On February 24th, 2015, 11:52 a.m. UTC, <b>Kai Uwe \
Broulik</b> wrote:</p> <blockquote style="margin-left: 1em; border-left: 2px solid \
#d0d0d0; padding-left: 10px;">
<table width="100%" border="0" bgcolor="white" style="border: 1px solid #C0C0C0; \
border-collapse: collapse; margin: 2px padding: 2px;"> <thead>
<tr>
<th colspan="4" bgcolor="#F0F0F0" style="border-bottom: 1px solid #C0C0C0; \
font-size: 9pt; padding: 4px 8px; text-align: left;"> <a \
href="https://git.reviewboard.kde.org/r/122673/diff/1/?file=350723#file350723line495" \
style="color: black; font-weight: bold; text-decoration: \
underline;">src/declarativeimports/core/framesvgitem.cpp</a> <span \
style="font-weight: normal;">
(Diff revision 1)
</span>
</th>
</tr>
</thead>
<tbody style="background-color: #e4d9cb; padding: 4px 8px; text-align: center;">
<tr>
<td colspan="4"><pre style="font-size: 8pt; line-height: 140%; margin: 0; ">void \
FrameSvgItem::componentComplete()</pre></td>
</tr>
</tbody>
<tbody>
<tr>
<th bgcolor="#e9eaa8" style="border-right: 1px solid #C0C0C0;" \
align="right"><font size="2">495</font></th> <td bgcolor="#fdfebc" width="50%"><pre \
style="font-size: 8pt; line-height: 140%; margin: 0; "> <span \
class="n">m_frameSvg</span><span class="o">-></span><span \
class="n">setDevicePixelRatio</span><span class="p">(</span><span \
class="n">qMax</span><span class="o"><</span><span class="n">qreal</span><span \
class="o">></span><span class="p">(</span><span class="mf">1.0</span><span \
class="p">,</span> <span class="n">floor</span><span class="p">(</span><span \
class="n"><span class="hl">m_units</span></span><span class="p"><span \
class="hl">.</span></span><span class="n">devicePixelRatio</span><span \
class="p">())));</span></pre></td> <th bgcolor="#e9eaa8" style="border-left: 1px \
solid #C0C0C0; border-right: 1px solid #C0C0C0;" align="right"><font \
size="2">495</font></th> <td bgcolor="#fdfebc" width="50%"><pre style="font-size: \
8pt; line-height: 140%; margin: 0; "> <span class="n">m_frameSvg</span><span \
class="o">-></span><span class="n">setDevicePixelRatio</span><span \
class="p">(</span><span class="n">qMax</span><span class="o"><</span><span \
class="n">qreal</span><span class="o">></span><span class="p">(</span><span \
class="mf">1.0</span><span class="p">,</span> <span class="n">floor</span><span \
class="p">(</span><span class="n"><span class="hl">qApp</span></span><span \
class="o"><span class="hl">-></span></span><span \
class="n">devicePixelRatio</span><span class="p">())));</span></pre></td> </tr>
</tbody>
</table>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: \
inherit;">Doesn't QWindow have a devicePixelRatio()? That way we could, one day, have \
separate scaling per monitor.</p></pre> </blockquote>
<p>On February 24th, 2015, 11:56 a.m. UTC, <b>Marco Martin</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">yep, \
should eventually use that (tough i'm not sure yet) i should really find a way to \
have one units instance per screen (or qwindow) instead per qqmlengine, that's not \
going to be super easy compared how is done now</p></pre> </blockquote>
<p>On February 24th, 2015, 4:28 p.m. UTC, <b>Xuetian Weng</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">What \
would be the qApp->devicePixelRatio() value if QT_DEVICE_PIXEL_RATIO set to auto ? \
...</p></pre> </blockquote>
<p>On February 24th, 2015, 4:34 p.m. UTC, <b>David Edmundson</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;"> <pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">it's \
automatically set to 1.0 or 2.0 depending on your screen</p></pre> </blockquote>
</blockquote>
<pre style="margin-left: 1em; white-space: pre-wrap; white-space: -moz-pre-wrap; \
white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p \
style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: \
inherit;">I realised now I didn't read your question properly.</p> <p style="padding: \
0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">It's \
the DPI of the highest screen. Rationale being if you supply a high DPI pixmap to a \
paintdevice with a devicePixelRatio of 1, then nothing bad will happen. It will just \
be implicitly scaled down.</p></pre> <br />
<p>- David</p>
<br />
<p>On February 22nd, 2015, 1:39 p.m. UTC, Marco Martin wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="12" style="border: \
1px #888a85 solid; border-radius: 6px; -moz-border-radius: 6px; \
-webkit-border-radius: 6px;"> <tr>
<td>
<div>Review request for Plasma.</div>
<div>By Marco Martin.</div>
<p style="color: grey;"><i>Updated Feb. 22, 2015, 1:39 p.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
plasma-framework
</div>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" \
style="border: 1px solid #b8b5a0"> <tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: \
-moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: \
break-word;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: \
inherit;white-space: inherit;">(still in progress but here for feedback) when \
QT_DEVICE_PIXELRATIO is something different from 1, the pixmaps generated by Svg will \
be scaled up to give a proper texture.</p> <p style="padding: 0;text-rendering: \
inherit;margin: 0;line-height: inherit;white-space: inherit;">This is complementary \
but not replacing our current approach: the pixelratio that can be accessed by units \
is now in relation to the qt pixel ratio, spacings are also adjusted accordingly \
(therefore, spaces and sizes won't need an integer value like pixelratio)</p> <p \
style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: \
inherit;">svg introduces also a scaleFactor property (that is pretty much like its \
old pixelRatio) basically, scalefactor, will scale both the textures <em \
style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: \
normal;">and</em> all the reported sizes, (old method) pixelratio just scales \
textures without altering measures (like qt pixelratio likes) they are now both used \
and combined, so a) we can have this working before supporting officially qt \
pixelratio when will be good enough but b) keeping the old mwthod working for the \
time being c) by using both at the sae time we can at least scale sizes of values != \
from integers, for screens that are too dense for 1 and not enough for 2</p></pre> \
</td> </tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>src/declarativeimports/core/framesvgitem.cpp <span style="color: \
grey">(dae8a4f)</span></li>
<li>src/declarativeimports/core/svgitem.cpp <span style="color: \
grey">(570c1c3)</span></li>
<li>src/declarativeimports/core/units.h <span style="color: \
grey">(6c038ba)</span></li>
<li>src/declarativeimports/core/units.cpp <span style="color: \
grey">(a740145)</span></li>
<li>src/plasma/private/svg_p.h <span style="color: grey">(a31d0ac)</span></li>
<li>src/plasma/svg.h <span style="color: grey">(0bcbd7a)</span></li>
<li>src/plasma/svg.cpp <span style="color: grey">(0a0db5e)</span></li>
</ul>
<p><a href="https://git.reviewboard.kde.org/r/122673/diff/" style="margin-left: \
3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>
--===============0872269998654100794==--
[Attachment #3 (text/plain)]
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic