<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - PDF saves a very erratic size"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=119634#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - PDF saves a very erratic size"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=119634">bug 119634</a>
from <span class="vcard"><a class="email" href="mailto:miscellaneous@paintdrawer.co.uk" title="DM <miscellaneous@paintdrawer.co.uk>"> <span class="fn">DM</span></a>
</span></b>
<pre>What would really help with tracking such bugs as these - and in fact most bugs
- would be to have a 'recorder' feature on LibreOffice, that a user having a
problem can switch on so that it makes a copy of the file and then records all
the actions and steps they make, and when a problem occurs they can send you
the file that was opened with the action record that then happened to it, which
may be 500 actions, but it may have been the 10th action of the 500 that
generated the problem, the programmers could step through and watch for it to
happen using a halving method (apply the first 250 steps to see if the problem
was caused, then 125 steps to the side of that (i.e. 125 or 375 steps) etc,
then 63, 31, 15 etc) which would quickly catch how just about every problem
occurred.
David</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>