Forced page break in writeFlashHtmlText is unnecessary

[GoogleCodeExporter]

What steps will reproduce the problem?
1. call writeFlashHtmlText() more than once on a page.

What is the expected output? What do you see instead?
I would expect to be able to write HTML formatted text more than once on a
page. Instead, there is a forced page break (line #3649). This should be
optional or better yet removed altogether. If I need to break the page, I
can make an additional method call for that. The way it stands now, I need
to modify the PDF class every time there is an update.

What version of the product are you using? On what operating system?
0.1.5 RC

Please provide any additional information below.
Thanks for all your hard work guys. This truly is an impressive library.

Original issue reported on code.google.com by modernde...@gmail.com on 2 Mar 2010 at 8:50

[GoogleCodeExporter]

I agree. It's a very annoying and unexpected behaviour. Please remove it!

Original comment by plath...@gmail.com on 14 Apr 2010 at 12:28

[GoogleCodeExporter]

Note: if you comment out the line in PDF.as that adds the forced page break, 
watch out for this statement in the renderline function: "addPage( 
currentPage.clone());"

That is where it determines if a page break is needed for a text cell being 
added with writeFlashHTMLText, but instead of adding a new blank page, it adds 
a clone (including content) of the current page. So, on p. 2, you would have 
all of the content from p. 1 duplicated, plus the new content written on top of 
it.

Original comment by daryllbe...@gmail.com on 17 Jan 2011 at 5:25

[GoogleCodeExporter]

 - http://code.google.com/p/alivepdf/issues/detail?id=204 => fixed in r281. Now Fontsize are correctly processed. Please refer to the "writeFlashHtmlText how-to" in http://code.google.com/p/alivepdf/wiki/APIAdditions .

Original comment by felix.ge...@gmail.com on 8 Oct 2011 at 8:43

• Changed state: Fixed

[GoogleCodeExporter]

Is this really solved ?
There's still on line 3950 :
//Set current y off the page to force new page.
currentY += currentPage.h;
I don't understand why ?

Original comment by fxmarko...@gmail.com on 12 Dec 2012 at 8:40