<html>
<head>
<base href="https://bugs.documentfoundation.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - clean VirtualDevice constructor ..."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=86249#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - clean VirtualDevice constructor ..."
href="https://bugs.documentfoundation.org/show_bug.cgi?id=86249">bug 86249</a>
from <span class="vcard"><a class="email" href="mailto:michael.meeks@collabora.com" title="Michael Meeks <michael.meeks@collabora.com>"> <span class="fn">Michael Meeks</span></a>
</span></b>
<pre>I suspect the ambiguity is unpleasant - ie. if there are two constructors with
similar arguments we should have nice, readable, descriptive enum that
distinguishes between the two use-cases; rather than a random number that is
always the same value nAlphaBitCount added to the end =)
It seems we have:
ScopedVclPtrInstance<VirtualDevice> pDevice(&aData, Size(1, 1),
DeviceFormat::DEFAULT);
I wonder if we could overload something into the vdev creation along those
lines; not sure.
Beyond that the bigger problem is that VirtualDevices get created at a 1x1 size
initially - complete with OS resources behind them, which are slow & expensive
to create - and then we re-size them deleting the original stuff =) really the
creation needs to have a smoother flow that passes in the size correctly.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>