Bug 207196

Summary: StyledTextPrintOptions should offer place holder for page count
Product: [Eclipse Project] Platform Reporter: Dani Megert <daniel_megert>
Component: SWTAssignee: Felipe Heidrich <eclipse.felipe>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3 CC: heath.borders
Version: 3.4   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Dani Megert CLA 2007-10-23 12:39:04 EDT 
I20071023-0800.

StyledTextPrintOptions should offer place holder for page count. Currently there's only a place holder for the page number.
Comment 1 Felipe Heidrich CLA 2007-11-13 15:18:48 EST 
page count == total number of pages to be print ?

In the case scope == PAGE_RANGE; pageStart == 10; pageEnd == 12.
Page count is 3 in this case.

I can see the app setting the footer to
"page <page> of <pagecount>"
and it would get, page 10 of 3, page 11 of 3, page 12 of 3.


Maybe it would be better to offer page_start and page_end intead ?
Comment 2 Dani Megert CLA 2007-11-14 02:40:45 EST 
Sorry, with page count I meant the total number of pages i.e. you would get
page 10 of 30, page 11 of 30, page 12 of 30.

This problem is dealt with quite differently on various apps. Some even offer to set the start page number, so that your example could end up being
1 of 3, 2 of 3, 3 of 3.

Having pageStart/End would also be useful but I guess I'd use the total page count.
Comment 3 Felipe Heidrich CLA 2007-11-14 11:51:21 EST 
That is little bit more difficult cause I don't have the total number of pages when print start.
I would have to initialize and measure all paragraphs to find the height of the document (number of pages == document height / page height). Then I would have to initialize (again) and draw each paragraph.

this would make print slower.
Comment 4 Dani Megert CLA 2007-11-14 12:01:35 EST 
How much slower do you think? Couldn't you reuse the information you gain from the first run? Also, why would pageEnd be cheaper to compute when I print everything?
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:38:30 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.