<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Use floating point for glyph positioning in VCL"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=103322#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Use floating point for glyph positioning in VCL"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=103322">bug 103322</a>
from <span class="vcard"><a class="email" href="mailto:khaledhosny@eglug.org" title="Khaled Hosny <khaledhosny@eglug.org>"> <span class="fn">Khaled Hosny</span></a>
</span></b>
<pre>(In reply to Mike Kaganski from <a href="show_bug.cgi?id=103322#c11">comment #11</a>)
<span class="quote">> Do we have a (compact) API subset that needs to be changed from int to
> double to start the change?</span >
I’d start with the “Text functions” section in include/vcl/outdev.hxx and go
down and up from there.
We will need to switch from tools::Point, tools::Rectangle etc. to
basegfx::B2DPoint, basegfx::B2DRectangle, not just int to float/double. May be
using basegfx::B2IPoint first since they are still int-based, so the first
round would focus on the difference in semantics and API between tools and
basegfx, then next round would tackle the actual floating pint conversion.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>