# Issues

Issue #67 resolved

# Vertical offset of slide content for pages > 1 with current PGF

Anonymous created an issue

Hello,

I'm using the CVS version of PGF and noticed a problem with content placement on the slides. The first page is placed correctly but subsequent pages have a slightly shifted downwards. This is well observable as narrow white border at the top when using a theme with colored box at the top or when adding a background grid. I can reproduce this with any of the example presentations.

The problem occurs with the Debian-delivered beamer-3.07 but also beamer-3.10 download from here. It appears to be connected to current PGF, as the problem disappears when resetting my PGF CVS tree to version 2.00. (However I need the current one for pgfplots.)

Regards Stefan

Hi Stefan,

I already reported this behaviour in beamer-class list and after deciding that the problem was with pgf cvs version I filled a bug report in pgf's site and sent a email to pgf-users list. Until now I haven't received any response.

Best regards,

Ignasi

Bump! I don't know how to eliminate this comment!

Hello Ignasi,

yes, somehow you're right... On the other hand it's not that clear that PGF is the one to blame. It seems there is a connection of the bug to using recent hyperref and geometry packages as well but I wasn't able to evaluate this further. Also, I have no clue which feature of PGF is involved nor a simple PGF test case to show it. That's why I decided to file this bug where it appears - in beamer. I hope the developers here can find out if it's really in beamer or in one of the dependencies and then file an appropriate bug report there...

Best regards,

Stefan

1. repo owner

To be honest, I don't know who is to blame. I doubt that there is any connection with hyperref, but geometry could be involved.

It could be that it's not a bug at all, but just some change that happened in PGF CVS that Beamer isn't compatible with.

Ignasi, any news on this from pgf-users mailing list?

Hello Vedran,

yesterday I wrote again to pgf-users list and today I've received next message from Christian Feuersänger (pgfplots' developer). I don't know who is Stefan Tibus. Hope it helps.

Ignasi

-----------------

Hello Ignasi,

you are right, there is such a problem (and not only on your machine).

I tried to track it down several weeks ago, but I failed to identify its source in the attempt. By using an old TeX installation and manually installing new versions of other packages, I concluded that it is an incompatibility between pgf CVS and some recent version of another package which is loaded by beamer (Details are on another computer; I can't access it from here). In the meantime, Stefan Tibus wanted to contact the beamer team if I am not mistaken (I've been quite busy in-between). I'll contact Stefan if he has news.

Best regards

Christian

2. repo owner

OK, that's much better. I should apparently do some experiments, but can't promise when, hopefully before next version of PGF appears on CTAN.

Hello,

I am part of the development team of PGF (my answer to Ignasi's request is posted above).

We are currently working on a new stable PGF version and, since beamer+pgf is a very important issue, I would like to find out about the status of this problem.

Did you already identify the source of the problem? I haven't been able to really pin it down... and my experience with the implementation of beamer is - admittadly - not so deep as to find it.

As far as I know, the minimal example

\documentclass{beamer}

\setbeamercolor{structure}{bg=brown}

\begin{document}

\begin{frame}{Frame 1} \end{frame}

\begin{frame}{Frame 2} \end{frame}

\end{document}

should reproduce the bug, given a recent TeX installation ( I don't have one here on this computer ).

Please let me know anything you already found with respect to this issue such that I can decide if I need to look into it before a new pgf version is released. Our current timetable is to release pgf at the end of next week (afterwords, I don't have that much spare-time left to do so).

Best regards

Christian

Hello,

I have tracked the bug. Now, I am pretty sure that it occurs in a recent version of hyperref.

To see this, you can create a file ./hyperref.sty with contents \def\hypersetup#1{} \def\hyperlink#1#2{} \def\pdfstringdefDisableCommands{} \def\Acrobatmenu#1#2{}

and the bug will be gone.

Second, if you eliminate that temporary file again and you write

\documentclass{beamer}

\setbeamercolor{structure}{bg=brown}

\makeatletter \let\Hy@FixNotFirstPage=\relax \makeatother

\begin{document}

\begin{frame}{Frame 1} \end{frame}

\begin{frame}{Frame 2} \end{frame}

\end{document}

the bug is gone. The macro Hy@FixNotFirstPage is something strange, I will contact the hyperref authors for support. But at least the work-around above works.

Best regards

Christian

3. repo owner

Thank you!

If hyperref authors find that macro neccessary, I can add \let\Hy@FixNotFirstPage=\relax to \beamer@lasminutepatches{}.

By the way, how come that bug doesn't happen with PFG 2.0?

Vedran,

I've received good news from Christian (see below). I've tested new pgf-cvs and it works.

Ignasi -------- Dear Ignasi,

Heiko Oberdiek (author of hyperref package) helped to identify the problem as bug in PGF and he suggested a bugfix.

I have just submitted the bugfix to PGF CVS.

Consequently, my work-around presented in a previous mail is obsolete now.

Thanks for reporting!

Best regards

Christian

4. repo owner

Thanks for reporting back. PGF 2.10 is released now, and I will mark this as resolved.