Hi,
On Monday 04 July 2005 00:17, Alex Roitman wrote:
> > * If I select "Indicate non-birth relationships with dotted lines", the
> > generated report (and also dot file), marks *all* relations as
> > dotted. I was using the example database and "Ancestors of Smith, Edwin
> > Michael" as the filter.
>
> This should be fixed in CVS. Please let me know if it still misbehaves.
Verified.
> > * Although I select 1x1 pages for the output, the report generates 4
> > pages (of which 3 have *very* little content). This happens with
> > margins set to zero. If I set the margins to one, then there's only
> > one page of output. A possible explanation for this could be that with
> > zero margins set in the GUI, the generated dot file still seems to list
> > margin as 0.5 (and have only one margin value...):
> > -----
> > * margins top/bottom : 0.0
> > * left/right : 0.0
> > * pages horizontal : 1
> > * vertical : 1
> > * page width : 8.26771653543in
> > * height : 11.6929133858in
> > ...
> > center=1;
> > margin=0.5;
> > size="8.3,11.7";
> > page="8.3,11.7";
> > ------
>
> The dot format seem to want one margin value, default is 0.5 in.
> The GUI-provided margins are used to calculate the height/width
> in "size" compared to "page". Zero margins mean that size equals
> page.
>
> I am not certain what is the role of "margin" value
Dot man page says:
"sets the page margin (included in the page size)."
Report "page" .dot setting AFAIK comes from the Gramps/printing page
setting. "size" sets bounding box of drawing, i.e. the "virtual" page size
(which can span multiple physical pages).
So... "margin" is associated with "page", whereas the margin settings in
the UI dialog are associated with the "size" (drawing bounding box).
> -- should we
> specify left/right or top/bottom margin? I thought of making it
> min(left_right,top_bottom), but I am not sure.
I tested setting:
margin=0.0
in the .dot file and that fixed the output for single page with top/bottom
and left/right margins set to 0.0 in the UI (both for single and multiple
pages).
However, when looking at the code:
self.f.write("margin=0.5;\n")
self.f.write("size=\"%3.1f,%3.1f\";\n" % (
(self.width*self.hpages)-(self.lr_margin*2)
-((self.hpages-1)*1.0),
(self.height*self.vpages)-(self.tb_margin*2)
-((self.vpages-1)*1.0))
)
I'm not sure what the "-((self.hpages-1)*1.0)" is for.
Is "*1.0" supposed to be "*2*margin"?
For printing you probably need a page margin in addition to the bounding box
margin as all printers (e.g. my deskjet) cannot print to the full page
size... I.e. unfortunately it cannot be zero. In some printers some margin
(bottom?) can be as large as one inch.
While testing this, I noticed another oddity:
- After setting the margins once to zero, changing them to another value,
OK'ing the dialog and reopening the dialog still presented the margins as
zero. Don't they get saved properly?
- Eero
> If you know or can find the proper margin value by experimenting,
> just let me know and I implement it. If it means horizontal
> margin then maybe we need to give it just left/right value?
>
> Alex
|