Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Patch] Real transparency for box shadows #161

Closed
josephwright opened this issue Oct 13, 2011 · 8 comments
Closed

[Patch] Real transparency for box shadows #161

josephwright opened this issue Oct 13, 2011 · 8 comments
Labels
enhancement New feature or request

Comments

@josephwright
Copy link
Owner

Originally reported by: manulopezibanez (Bitbucket: manulopezibanez, GitHub: Unknown)


Source: http://old.nabble.com/-Patch--Real-transparency-for-shadows-td25529391.html

I have tested it, and it makes the shadows of boxes transparent.

My current beamer is beamer 2007/03/11 cvs version 3.07

Is there any problem to apply them? Do you need more testcases? Maybe this is fixed in the latest version?


@josephwright
Copy link
Owner Author

Original comment by Anonymous:


It is sufficient to just add the two variables
\newdimen\bmb@boxwidth
\newdimen\bmb@boxheight
to the beginning
and to override beamers \endbeamerboxesrounded with the one from the patch.
this can for example be done in your own beamer template by adding the \def\endbeamerboxesrounded
part at the end of your theme.
Right now I have found no issues with this approach so far...

@josephwright
Copy link
Owner Author

Original comment by Joseph Wright (Bitbucket: josephwright, GitHub: josephwright):


Use real transparency for box shadows (fixes issue #161)

@josephwright
Copy link
Owner Author

Original comment by Joseph Wright (Bitbucket: josephwright, GitHub: josephwright):


Back out use of real transparency of shadows

This reopens issue #161 and closes issue #192

The problem here is that while the code works for pdflatex, if fails
with the latex + dvips + ps2pdf and latex + dvipdfmx routes. I suspect an
issue here is actually with the pgf back-end, but for the moment we want
something which at least works!

@josephwright
Copy link
Owner Author

Original comment by Joseph Wright (Bitbucket: josephwright, GitHub: josephwright):


Given the issues this causes, unless there is good evidence for a fix in the pgf drivers it has to be WONTFIX.

@josephwright
Copy link
Owner Author

Original comment by Ignacio Fernández Galván (Bitbucket: Jellby, GitHub: Jellby):


Can't the code detect if pdflatex or latex + dvi... is being used? Or at least enable real transparency with some option (and warn the user that it will only work in some cases)?

@josephwright
Copy link
Owner Author

Original comment by Joseph Wright (Bitbucket: josephwright, GitHub: josephwright):


That's entirely doable but then means that the outcome depends on the compilation route: if at all possible I'd rather not have that happening.

@josephwright
Copy link
Owner Author

Original comment by manulopezibanez (Bitbucket: manulopezibanez, GitHub: Unknown):


This patch started giving trouble:

./beamerouterthemeshadow.sty:97: LaTeX Error: Command \beamer@@tmpOp@frametitle@shadow theme already defined.
Or name \end... illegal, see p.192 of the manual.

but I haven't had time to find a fix. However, the output still looks right (with pdflatex).

Document Class: beamer 2012/10/15 development version 3.24 A class for typesetting presentations (rcs-revision 24853e6b98cf)

@josephwright
Copy link
Owner Author

Original comment by manulopezibanez (Bitbucket: manulopezibanez, GitHub: Unknown):


Ah no, this was my mistake. It still works flawlessly. Just add the files to your current directory.

I'm sure that the whole files are not needed, but it is difficult for me to understand what is the precise fix here. If someone could produce a smaller fix that would be very much appreciated.

@josephwright josephwright added major enhancement New feature or request labels Nov 27, 2016
josephwright added a commit that referenced this issue Nov 27, 2016
This reopens issue #161 and closes issue #192

The problem here is that while the code works for pdflatex, if fails
with the latex +  dvips + ps2pdf and latex + dvipdfmx routes. I suspect an
issue here is actually with the pgf back-end, but for the moment we want
something which at least works!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant