After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 172292 - Printing: non working days misaligned
Printing: non working days misaligned
Status: RESOLVED FIXED
Product: planner
Classification: Other
Component: Printing
0.13
Other All
: Normal normal
: 0.14
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2005-03-31 19:59 UTC by fmoraes
Modified: 2009-08-13 01:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test project demonstrating problem (4.45 KB, text/plain)
2005-03-31 20:01 UTC, fmoraes 		Details

Description fmoraes 2005-03-31 19:59:23 UTC 
Please describe the problem:
Non working days are misaligned with the header in the print previw/print output.

See the attached file

Steps to reproduce:
1. use the attached file
2. print preview



Actual results:
Non working days are misaligned with headers.

Expected results:
Non working days aligned with headers.

Does this happen every time?
Yes.

Other information:
Comment 1 fmoraes 2005-03-31 20:01:43 UTC 
Created attachment 39523 [details]
test project demonstrating problem

If the project start time is changed, the problem goes away. It seems like the
call to align the time in planner-gantt-print.c is at fault:

	/* Third pass, add background shading for non-work intervals. */
	for (row = 0; row < data->rows_of_pages; row++) {

		t0 = mrp_time_align_day (data->start);

Either the headers should do the same thing or data->start should be used
directly.
Comment 2 Richard Hult 2005-04-04 18:57:21 UTC 
Hm, I remember doing that for a reason, I think it might have been a workaround
for a bug in the project start time that has been fixed since. I'll take a look,
thanks for the patch!
Comment 3 Richard Hult 2005-04-16 20:27:11 UTC 
Ah, it was a test file, not a patch :) Anyway, fixed in CVS.