Hi,
I'm adding an .png image to .docx. In Word the image is displayed correctly. When exporting to .PDF the image is rendered all black.
Test-Image:
https://ibb.co/r2YcmNy
Could you please have a look at this issue?
King regards,
Orest.
Search found 5 matches
- Tue Dec 15, 2020 8:53 am
- Forum: AXWWriter and DOCXReadWrite
- Topic: Issue: .png image with transparancy rendered black in .PDF
- Replies: 1
- Views: 1761
- Tue Dec 15, 2020 8:35 am
- Forum: AXWWriter and DOCXReadWrite
- Topic: Issue: Table not rendered properly in PDF on pagebreak
- Replies: 1
- Views: 1747
Issue: Table not rendered properly in PDF on pagebreak
Hi, I have a .docx file with a simple multi-column table. The table starts in the middle of page 1 and ends on page 2. When exporting to PDF the table draws a vertical-line after the last row on page 1 down to the bottom of the page. Illustration: |---|----------|----------| |-1-|-a--------|-a------...
- Tue Dec 15, 2020 8:26 am
- Forum: AXWWriter and DOCXReadWrite
- Topic: Hints and warnings...
- Replies: 1
- Views: 1631
Hints and warnings...
Hi, i'm compiling directly from source and am getting some hints and warnings when including your units. Could you switch your {$IFDEF DEBUG} to some other condition please? It conflicts with users DEBUG conditions. Could you deliver 0-warnings, 0-hints sources by default, please? I have to disable ...
- Tue Dec 15, 2020 8:16 am
- Forum: AXWWriter and DOCXReadWrite
- Topic: Issue: Page columns not handled properly
- Replies: 1
- Views: 1758
Issue: Page columns not handled properly
Hi, i have a multi page .docx file. Page 1 and 2 are single-column pages, page 3 is formatted as a 2-columns page. Following code results in loosing the 2-colums format setting of page 3 in the file. DocX := TDOCXReadWrite.Create(nil); try DocX.LoadFromFile(FFileName); DocX.SaveToFile(FFileName)); f...
- Tue Dec 15, 2020 8:10 am
- Forum: AXWWriter and DOCXReadWrite
- Topic: Memory Leak
- Replies: 3
- Views: 4873
Re: Memory Leak
Hi, this leak happens too over here. This is the callstack, maybe it helps to find the issue. I'm compiling directly from sources by the way. King regards, Orest. A memory block has been leaked. The size is: 36 This block was allocated by thread 0x42EC, and the stack trace (return addresses) at the ...