Empty Header and Footer problem
Posted: Mon Nov 20, 2023 8:03 am
Hello Sergey,
saveing a DocX / RTF with ScaleRichView generates a header and footer, also if there is none, with an empty paragraph which uses the document "default?" first style?
In some of my cases the height of header and footer is set to zero or even a very small value and the pages borders too.
But if I open the new saved files with MS Word - the header/footer height is increased according to the empty paragraph's font height.
Which moves the whole layout verticaly.
Original DOCX in Word @100% After save with ScaleRichView you can see the newly generated paragraph - this changes the print result and PDF export of MS Word to move the whole layout.
(If I deleted the empty paragraph all is fine again)
Is there a way in ScaleRichView to suppress the storage of empty headers and footers?
Useing plain TRichView I can do something like this before saveing:
if rvHeader_Normal.RVData.IsEmpty then
rvBody.SetHeader(nil, TRVHFType.rvhftNormal);
- but I think this should happen inside the default save logic?
With best regards
André
saveing a DocX / RTF with ScaleRichView generates a header and footer, also if there is none, with an empty paragraph which uses the document "default?" first style?
In some of my cases the height of header and footer is set to zero or even a very small value and the pages borders too.
But if I open the new saved files with MS Word - the header/footer height is increased according to the empty paragraph's font height.
Which moves the whole layout verticaly.
Original DOCX in Word @100% After save with ScaleRichView you can see the newly generated paragraph - this changes the print result and PDF export of MS Word to move the whole layout.
(If I deleted the empty paragraph all is fine again)
Is there a way in ScaleRichView to suppress the storage of empty headers and footers?
Useing plain TRichView I can do something like this before saveing:
if rvHeader_Normal.RVData.IsEmpty then
rvBody.SetHeader(nil, TRVHFType.rvhftNormal);
- but I think this should happen inside the default save logic?
With best regards
André