tangs7 / alivepdf

Automatically exported from code.google.com/p/alivepdf
0 stars 0 forks source link

font size not consistent when message body moves to the next page #338

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
This seems to be a regression because it didn't happen in the older versions. 
What happens is that when adding a large body of text that scrolls over to the 
next page, the size of the font will all of a sudden shrink. So for example:

pdf.setFont(someFont, 12);
pdf.setLeftMargin(10);
pdf.addMultiCell(170, 6, someReallyLongText, 0, "L");

It'll display correct in the first page, but when the text rolls over to the 
next page, the font size shrinks to another size.

I'm using AlivePDF 0.1.5 RC, revision 277 from SVN. 

Original issue reported on code.google.com by sor...@gmail.com on 12 Oct 2011 at 5:07

GoogleCodeExporter commented 9 years ago
thanks for reporting the issue.

I cannot reproduce the issue in the revision 286 (you can look at the attached 
pdf file obtain by executing the AlivePDFTestIssue338.mxml application of the 
AlivePDFTest project)

Could you confirm there is still an issue in r286, and if so attach a small 
application and pdf result.

Félix

Original comment by felix.ge...@gmail.com on 15 Oct 2011 at 2:19

Attachments:

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Hi there,

I attached a mini program and PDF result of the program. Basically what happens 
is that on the second page of the PDF, at the very top, the last portion of the 
paragraph (starting with "consequatur") has a slightly smaller text than the 
font on the other parts of the page. You'll see that it shrinks itself even 
though I hadn't made any changes to that font size. This was not an issue in 
the past (not sure what revision it was, probably prior to 0.1.5).

Let me know if you need anything else. Thanks for looking into this!

Original comment by sor...@gmail.com on 25 Oct 2011 at 8:59

Attachments:

GoogleCodeExporter commented 9 years ago
Hi,

I cannot reproduce the issue with the code in r289.

Could you tell me, if you have the same result when running the 
AlivePDFTestIssue338_2.mxml application (I attached it, and I also commited it 
in the r289 in the AlivePDFTest project) ?

Original comment by felix.ge...@gmail.com on 27 Oct 2011 at 6:55

Attachments:

GoogleCodeExporter commented 9 years ago
Hi there,

I found that if I updated to r289 as well, the issue goes away. Looks good now, 
thanks! This issue can be closed. 

Original comment by sor...@gmail.com on 27 Oct 2011 at 8:40

GoogleCodeExporter commented 9 years ago
Hey, 
great to know that the problem is solved.

Thanks again for reporting the issue.

Original comment by felix.ge...@gmail.com on 27 Oct 2011 at 11:50