Are package animate and beamer still compatible? [closed]












3















A minimal example below



documentclass{beamer}
usepackage{animate}

begin{document}
frame{
Hello, world.
}
end{document}


Gives me:



! Undefined control sequence.
<argument> ...g_pbs_bop_seq {##1}}box_use_drop:N
@outputbox hbox_overlap_...
l.7 }









share|improve this question













closed as off-topic by samcarter, AlexG, Zarko, jfbu, Phelype Oleinik Jan 14 at 11:25



  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.









  • 4





    That error suggests your expl3 version doesn't match animate: what TeX system do you have?

    – Joseph Wright
    Jan 13 at 9:56






  • 3





    update your TeX system and try a again

    – Herbert
    Jan 13 at 9:56






  • 4





    The example compiles without error for me. What versions of beamer, animate and expl3 are you using? I have beamer 2018/12/02 v3.55, animate.sty 2018/12/19 and expl3.sty 2019-01-01. You can find out your package versions easily if you add listfiles to the start of your MWE file, the versions will then be listed in a convenient table in the .log file.

    – moewe
    Jan 13 at 9:56








  • 4





    animate depends on expl3 via pdfbase.sty contained in media9. A full package update of the TeX distribution should fix everything.

    – AlexG
    Jan 13 at 11:07






  • 4





    I'm voting to close this question as solved by update

    – samcarter
    Jan 14 at 11:04
















3















A minimal example below



documentclass{beamer}
usepackage{animate}

begin{document}
frame{
Hello, world.
}
end{document}


Gives me:



! Undefined control sequence.
<argument> ...g_pbs_bop_seq {##1}}box_use_drop:N
@outputbox hbox_overlap_...
l.7 }









share|improve this question













closed as off-topic by samcarter, AlexG, Zarko, jfbu, Phelype Oleinik Jan 14 at 11:25



  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.









  • 4





    That error suggests your expl3 version doesn't match animate: what TeX system do you have?

    – Joseph Wright
    Jan 13 at 9:56






  • 3





    update your TeX system and try a again

    – Herbert
    Jan 13 at 9:56






  • 4





    The example compiles without error for me. What versions of beamer, animate and expl3 are you using? I have beamer 2018/12/02 v3.55, animate.sty 2018/12/19 and expl3.sty 2019-01-01. You can find out your package versions easily if you add listfiles to the start of your MWE file, the versions will then be listed in a convenient table in the .log file.

    – moewe
    Jan 13 at 9:56








  • 4





    animate depends on expl3 via pdfbase.sty contained in media9. A full package update of the TeX distribution should fix everything.

    – AlexG
    Jan 13 at 11:07






  • 4





    I'm voting to close this question as solved by update

    – samcarter
    Jan 14 at 11:04














3












3








3








A minimal example below



documentclass{beamer}
usepackage{animate}

begin{document}
frame{
Hello, world.
}
end{document}


Gives me:



! Undefined control sequence.
<argument> ...g_pbs_bop_seq {##1}}box_use_drop:N
@outputbox hbox_overlap_...
l.7 }









share|improve this question














A minimal example below



documentclass{beamer}
usepackage{animate}

begin{document}
frame{
Hello, world.
}
end{document}


Gives me:



! Undefined control sequence.
<argument> ...g_pbs_bop_seq {##1}}box_use_drop:N
@outputbox hbox_overlap_...
l.7 }






beamer animate






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 13 at 9:48









ArnaudArnaud

1163




1163




closed as off-topic by samcarter, AlexG, Zarko, jfbu, Phelype Oleinik Jan 14 at 11:25



  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.




closed as off-topic by samcarter, AlexG, Zarko, jfbu, Phelype Oleinik Jan 14 at 11:25



  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.

If this question can be reworded to fit the rules in the help center, please edit the question.








  • 4





    That error suggests your expl3 version doesn't match animate: what TeX system do you have?

    – Joseph Wright
    Jan 13 at 9:56






  • 3





    update your TeX system and try a again

    – Herbert
    Jan 13 at 9:56






  • 4





    The example compiles without error for me. What versions of beamer, animate and expl3 are you using? I have beamer 2018/12/02 v3.55, animate.sty 2018/12/19 and expl3.sty 2019-01-01. You can find out your package versions easily if you add listfiles to the start of your MWE file, the versions will then be listed in a convenient table in the .log file.

    – moewe
    Jan 13 at 9:56








  • 4





    animate depends on expl3 via pdfbase.sty contained in media9. A full package update of the TeX distribution should fix everything.

    – AlexG
    Jan 13 at 11:07






  • 4





    I'm voting to close this question as solved by update

    – samcarter
    Jan 14 at 11:04














  • 4





    That error suggests your expl3 version doesn't match animate: what TeX system do you have?

    – Joseph Wright
    Jan 13 at 9:56






  • 3





    update your TeX system and try a again

    – Herbert
    Jan 13 at 9:56






  • 4





    The example compiles without error for me. What versions of beamer, animate and expl3 are you using? I have beamer 2018/12/02 v3.55, animate.sty 2018/12/19 and expl3.sty 2019-01-01. You can find out your package versions easily if you add listfiles to the start of your MWE file, the versions will then be listed in a convenient table in the .log file.

    – moewe
    Jan 13 at 9:56








  • 4





    animate depends on expl3 via pdfbase.sty contained in media9. A full package update of the TeX distribution should fix everything.

    – AlexG
    Jan 13 at 11:07






  • 4





    I'm voting to close this question as solved by update

    – samcarter
    Jan 14 at 11:04








4




4





That error suggests your expl3 version doesn't match animate: what TeX system do you have?

– Joseph Wright
Jan 13 at 9:56





That error suggests your expl3 version doesn't match animate: what TeX system do you have?

– Joseph Wright
Jan 13 at 9:56




3




3





update your TeX system and try a again

– Herbert
Jan 13 at 9:56





update your TeX system and try a again

– Herbert
Jan 13 at 9:56




4




4





The example compiles without error for me. What versions of beamer, animate and expl3 are you using? I have beamer 2018/12/02 v3.55, animate.sty 2018/12/19 and expl3.sty 2019-01-01. You can find out your package versions easily if you add listfiles to the start of your MWE file, the versions will then be listed in a convenient table in the .log file.

– moewe
Jan 13 at 9:56







The example compiles without error for me. What versions of beamer, animate and expl3 are you using? I have beamer 2018/12/02 v3.55, animate.sty 2018/12/19 and expl3.sty 2019-01-01. You can find out your package versions easily if you add listfiles to the start of your MWE file, the versions will then be listed in a convenient table in the .log file.

– moewe
Jan 13 at 9:56






4




4





animate depends on expl3 via pdfbase.sty contained in media9. A full package update of the TeX distribution should fix everything.

– AlexG
Jan 13 at 11:07





animate depends on expl3 via pdfbase.sty contained in media9. A full package update of the TeX distribution should fix everything.

– AlexG
Jan 13 at 11:07




4




4





I'm voting to close this question as solved by update

– samcarter
Jan 14 at 11:04





I'm voting to close this question as solved by update

– samcarter
Jan 14 at 11:04










1 Answer
1






active

oldest

votes


















0














Oops, the TeX distribution was not up to date. Updating it solved the problem, sorry for polluting StackExchange with my silly question.






share|improve this answer








New contributor




Arnaud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    So, I think we can close this question. This is the standard procedure for problems that can be solved by package updates.

    – AlexG
    Jan 14 at 11:03











  • (Don't feel offended by the close reason in the box below the question. It was automatically generated.)

    – AlexG
    Jan 14 at 21:08











  • That's OK, my mistake

    – Arnaud
    Jan 15 at 12:18


















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Oops, the TeX distribution was not up to date. Updating it solved the problem, sorry for polluting StackExchange with my silly question.






share|improve this answer








New contributor




Arnaud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    So, I think we can close this question. This is the standard procedure for problems that can be solved by package updates.

    – AlexG
    Jan 14 at 11:03











  • (Don't feel offended by the close reason in the box below the question. It was automatically generated.)

    – AlexG
    Jan 14 at 21:08











  • That's OK, my mistake

    – Arnaud
    Jan 15 at 12:18
















0














Oops, the TeX distribution was not up to date. Updating it solved the problem, sorry for polluting StackExchange with my silly question.






share|improve this answer








New contributor




Arnaud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    So, I think we can close this question. This is the standard procedure for problems that can be solved by package updates.

    – AlexG
    Jan 14 at 11:03











  • (Don't feel offended by the close reason in the box below the question. It was automatically generated.)

    – AlexG
    Jan 14 at 21:08











  • That's OK, my mistake

    – Arnaud
    Jan 15 at 12:18














0












0








0







Oops, the TeX distribution was not up to date. Updating it solved the problem, sorry for polluting StackExchange with my silly question.






share|improve this answer








New contributor




Arnaud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.










Oops, the TeX distribution was not up to date. Updating it solved the problem, sorry for polluting StackExchange with my silly question.







share|improve this answer








New contributor




Arnaud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this answer



share|improve this answer






New contributor




Arnaud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









answered Jan 14 at 11:01









ArnaudArnaud

1163




1163




New contributor




Arnaud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Arnaud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Arnaud is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1





    So, I think we can close this question. This is the standard procedure for problems that can be solved by package updates.

    – AlexG
    Jan 14 at 11:03











  • (Don't feel offended by the close reason in the box below the question. It was automatically generated.)

    – AlexG
    Jan 14 at 21:08











  • That's OK, my mistake

    – Arnaud
    Jan 15 at 12:18














  • 1





    So, I think we can close this question. This is the standard procedure for problems that can be solved by package updates.

    – AlexG
    Jan 14 at 11:03











  • (Don't feel offended by the close reason in the box below the question. It was automatically generated.)

    – AlexG
    Jan 14 at 21:08











  • That's OK, my mistake

    – Arnaud
    Jan 15 at 12:18








1




1





So, I think we can close this question. This is the standard procedure for problems that can be solved by package updates.

– AlexG
Jan 14 at 11:03





So, I think we can close this question. This is the standard procedure for problems that can be solved by package updates.

– AlexG
Jan 14 at 11:03













(Don't feel offended by the close reason in the box below the question. It was automatically generated.)

– AlexG
Jan 14 at 21:08





(Don't feel offended by the close reason in the box below the question. It was automatically generated.)

– AlexG
Jan 14 at 21:08













That's OK, my mistake

– Arnaud
Jan 15 at 12:18





That's OK, my mistake

– Arnaud
Jan 15 at 12:18



Popular posts from this blog

Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

ComboBox Display Member on multiple fields

Is it possible to collect Nectar points via Trainline?