Hi,
I am looking into the possibility of using TScaleRichView in an existing application. I Have linked the component to an external TRichView an TRVStyle, but it resulted in a pagination error that I have not been able to correct.
The component shows some text beetwen the pages, the bottom margin is not respected, and some text is not shown just after the page breaks.
I am using the latest full version of the component.
Any idea about what I am doing wrong? Should I post a screen capture? Thanks in advance,
Alexandre
pagination problem
-
- Site Admin
- Posts: 17602
- Joined: Sat Aug 27, 2005 10:28 am
- Contact:
As I tried to isolate the bug, I have found out what was causing the problem: the program was setting the margins of the associated RichViewEdit to zero.
Anyway, I have stumbled upon some possible problems:
a) ScaleRichViews does not use RichViewPixelsPerInch, even when its value is not zero;
b) ScaleRichView is printing the page numbers even when PageNoVisible=false; and
c) The routine DeleteBlankLines (posted in this forum), and some others that change and remove items directly, are causing the error "list index out of bounds."
Is there a workaround for b) ?
All the best, and thanks in advance.
Anyway, I have stumbled upon some possible problems:
a) ScaleRichViews does not use RichViewPixelsPerInch, even when its value is not zero;
b) ScaleRichView is printing the page numbers even when PageNoVisible=false; and
c) The routine DeleteBlankLines (posted in this forum), and some others that change and remove items directly, are causing the error "list index out of bounds."
Is there a workaround for b) ?
All the best, and thanks in advance.
-
- Site Admin
- Posts: 17602
- Joined: Sat Aug 27, 2005 10:28 am
- Contact:
It is supposed that margins of this RichViewEdit are changed by ScaleRichView. Do not change them directly.
a) Yes, ScaleRichView always assumes pixels-per-inch = 96, both on screen and on printing. It uses other mechanisms to provide a high resolution output. Actually, it's very convenient to ignore devices resolutions. For providing better RTF output, I recommend to set this variable to 96.
b) Ilya will check this problem
c) These routines must work correctly, providing that you call Format and ClearUndo after them.
a) Yes, ScaleRichView always assumes pixels-per-inch = 96, both on screen and on printing. It uses other mechanisms to provide a high resolution output. Actually, it's very convenient to ignore devices resolutions. For providing better RTF output, I recommend to set this variable to 96.
b) Ilya will check this problem
c) These routines must work correctly, providing that you call Format and ClearUndo after them.
-
- Site Admin
- Posts: 17602
- Joined: Sat Aug 27, 2005 10:28 am
- Contact:
-
- Site Admin
- Posts: 17602
- Joined: Sat Aug 27, 2005 10:28 am
- Contact: