I have some text and want to use WriteFTextEX to draw it over several pages of PDF
I want the first page only to start at about 1.5 inches down the page, then the second page to start near the top
If I use a boundary rectangle that starts 1.5 inches from the top, all the rest of the pages do that too, giving an unwanted gap at the top of many pages.
So I use a boundary rectangle that covers the page from top margin to bottom margin.
I add rows of endofline.windows to the start of my text, to move the text down the page a bit.
But WriteFTextEX seems to discard the blank lines, and starts right at the top.
Is there a way to stop this discarding of blank rows?
“Space ODOA” is also stripped.
First is that 18.1 plugin?
We had a fix in 18.1 as you can read in DynaPDF Plugin release notes.
Beta 18.1 from 2 March
I cant see any mention of this in the notes:
[quote]MBS Xojo Plugins 18.1 - 6th March 2018
Added GetSpaceWidth and GetTextWidth functions to DynaPDFMBS.
Fixed bug in DynaPDFMBS.WriteStyledText with extra new lines when switching alignment.
Fixed bug in DynaPDFMBS.WriteStyledText with switching font back to non-bold.
Fixed memory leak with DynaPDFFontInfoMBS objects.
Improved DynaPDFMBS.TranslateRawCode with new variant with more parameters.
Updated DynaPDF to version 184.108.40.206.[/quote]
I’ll download the versions from the 6th and see if it makes any difference.
Nope, 18.1 from 6 March has the same issue.
here is some simplified code to reproduce it: (including some spaces in case it stripped pure endoflines)
[code]dim eo as string = endofline.windows
dim txt as string
txt= " " + eo+" "+ eo+ " “+eo+” “+eo+” "+eo+ " "+eo+ " "+eo + “Hello”
call pdf.SetFont “Times”, pdf.kfsNormal, 12, true, pdf.kcp1252
call pdf.WriteFTextEX(20.0,20.0 , 200.0,300.0 ,0, txt)[/code]
Hello should appear about an inch down the page, but its right at the top
I see. I’ll ask Jens about this.
It is only leading blank lines
“Hello” plus end of lines plus “Hello” will leave a gap between the words
Any visible character is treated as the first character
the problem should be fixed now.
New plugin is here:
and this fix will of course be including in future releases.