-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
How does the margin_top argument of PageBreak work? #136
Comments
@stenci, thanks for reporting this. Here's a way to say the same thing that I would find more pleasant to read, for next time:
|
@hugetim I just re-read my post and it didn't look harsh, offensive or rantish in any way. At least to me, I will blame it on English not being my first language. I had a question, I investigated a little trying to understand, I failed, so I asked the question documenting my investigation. Here is my thought process while writing it:
It looks like I tried to be nice too hard and something went wrong. |
It has no effect in the designer. However it clearly wasn't working and the pdf you've shown works as I'd expect. Anyway I've fixed this in #137 by making it optional. |
Sounds like my mistake, then, @stenci. Sorry about that. I think I just
misinterpreted your tone, and I'm pretty new at this. It was indeed a
really informative report. (I wouldn't be able to explain such a thing at
all in a second language, myself.)
…---
typed with thumbs
On Fri, Sep 10, 2021, 8:51 PM stenci ***@***.***> wrote:
@hugetim <https://github.com/hugetim>
I apologize if my post sounded offensive or negative in any way. It was
not my intention at all.
I just re-read my post and it didn't look harsh, offensive or rantish in
any way. At least to me, I will blame it on English not being my first
language.
I had a question, I investigated a little trying to understand, I failed,
so I asked the question documenting my investigation.
Here is my thought process while writing it:
- I had a question and I opened an issue with the question as subject
- I said "I don't really need an answer" meaning I'm ok if you don't
want to waste your time addressing it
- "I don't understand" meaning it's ME not understanding
- "apparently useless" I intentionally put apparently right after
don't understand, again to blame it on myself
- "I thought I would bring it up here" again meaning it's not
important, I just want to share my thought in case you find it useful
- I added snapshots to show what I was looking at, to make it easier
for you to tell me if I was looking in the wrong place
It looks like I tried to be nice too hard and something went wrong.
Again, I apologize.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB63GLBDOCBGAMO4BT4TY63UBKY3FANCNFSM5D2C2NAA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I am building a multipage PDF by adding a few pages separated by
PageBreak
. Everything seems to be working well. I don't really need an answer here for completing my job, but since I don't understand what an undocumented and apparently useless, but required parameter does, I thought I would bring it up here.I tried using both
1
and500
integers and'1px'
and'500px'
strings with the following code, but the result doesn't change:I wasn't expecting it to require any parameter, but since one is required, I was expecting to see some difference in the top margin. instead it doesn't make any difference.
This is the result on the browser:
![image](https://user-images.githubusercontent.com/5955495/132915924-91610671-3698-4be6-a3e4-34f37b872a14.png)
and this is the result on the PDF"
![image](https://user-images.githubusercontent.com/5955495/132915456-caccf718-1d1f-48a1-bd31-8a4625b2d938.png)
The text was updated successfully, but these errors were encountered: