Git Product home page Git Product logo

Comments (4)

rchurchley avatar rchurchley commented on August 19, 2024

Thanks for the bug report. Awesome detective work!

I think I've tracked down the cause. The error occurs in the calculation of the width of the progress bar. When the presentation is compiled for the first time, \inserttotalframenumber defaults to 1 when it has no aux file to read from. Therefore, \ratio{\insertframenumber pt}{\inserttotalframenumber pt}, which we've assumed to be between 0 and 1, can actually become quite large. And if the width of the frame times this number ever exceeds 16384pt (about 18.9ft), then we get the error.

Fortunately, this problem is easily worked around by re-compiling. Once beamer has an aux file to read from, \inserttotalframenumber will be set to something reasonable and the error will no longer occur. Perhaps we should redefine \inserttotalframenumber to default to 100 to avoid this under reasonable usage?

from mtheme.

bgat avatar bgat commented on August 19, 2024

I fixed it by just setting the total frame number to 1 if it is ever less
than that.

b.g.

On Thu, Jun 11, 2015, 3:26 AM Ross Churchley [email protected]
wrote:

Thanks for the bug report. Awesome detective work!

I think I've tracked down the cause. The error occurs in the calculation
of the width of the progress bar. When the presentation is compiled for the
first time, \inserttotalframenumber defaults to 1 when it has no aux file
to read from. Therefore, \ratio{\insertframenumber
pt}{\inserttotalframenumber pt}, which we've assumed to be between 0 and
1, can actually become quite large. And if the width of the frame times
this number ever exceeds 16384pt (about 18.9ft)
http://tex.stackexchange.com/questions/139883/origin-and-formation-to-the-error-dimension-too-large,
then we get the error.

Fortunately, this problem is easily worked around by re-compiling. Once
beamer has an aux file to read from, \inserttotalframenumber will be set
to something reasonable and the error will no longer occur. Perhaps we
should redefine \inserttotalframenumber to default to 100 to avoid this
under reasonable usage?

Reply to this email directly or view it on GitHub
#70 (comment).

Bill Gatliff
[email protected]

from mtheme.

bgat avatar bgat commented on August 19, 2024

Seems like the default might actually be zero, in other words...

On Thu, Jun 11, 2015, 5:18 AM Bill Gatliff [email protected] wrote:

I fixed it by just setting the total frame number to 1 if it is ever less
than that.

b.g.

On Thu, Jun 11, 2015, 3:26 AM Ross Churchley [email protected]
wrote:

Thanks for the bug report. Awesome detective work!

I think I've tracked down the cause. The error occurs in the calculation of
the width of the progress bar. When the presentation is compiled for the
first time, \inserttotalframenumber defaults to 1 when it has no aux file
to read from. Therefore, \ratio{\insertframenumber
pt}{\inserttotalframenumber pt}, which we've assumed to be between 0 and 1,
can actually become quite large. And if the width of the frame times this
number ever exceeds 16384pt (about 18.9ft)
http://tex.stackexchange.com/questions/139883/origin-and-formation-to-the-error-dimension-too-large,
then we get the error.

Fortunately, this problem is easily worked around by re-compiling. Once
beamer has an aux file to read from, \inserttotalframenumber will be set to
something reasonable and the error will no longer occur. Perhaps we should
redefine \inserttotalframenumber to default to 100 to avoid this under
reasonable usage?

Reply to this email directly or view it on GitHub
#70 (comment).

Bill Gatliff
[email protected]

--

Bill Gatliff
[email protected]

from mtheme.

jakobbossek avatar jakobbossek commented on August 19, 2024

Thanks for fixing that.

from mtheme.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.