Question

I’m writing my thesis/dissertation and since its an on-going work I don’t always have the actual images ready for the figures I put into my document, but for various reasons want to automatically have it substitute a dummy figure in place when the included graphics file doesn’t exist. E.g. I can do something like \includegraphics[width=8cm]{\chapdir/figures/fluxcapacitor} (where \chapdir is a macro for my ‘current’ chapter directory, e.g. \def\chapdir{./ch_timetravel} and if there’s no ./ch_timetravel/figures/fluxcapacitor.jpg it’ll insert ./commands/dummy.jpg instead.

I’ve structured my macros (perhaps naïvely?) so that I have a macro (\figFileOrDummy) that determines the appropriate file to include by checking if the argument provided to it exists, so that I can call \includegraphics[properties]{\figFileOrDummy{\chapdir/figures/fluxcapacitor}}. Except I’m getting various errors depending on how I try to call this, which seem to suggest that I’m approaching the problem in a fundamentally flawed way as far as ‘good LaTeX programming’ goes.

Here’s the macro to check if the file exists (and ‘return’ either filename or the dummy filename):

\newcommand{\figFileOrDummy}[1]{%
    % Figure base name (no extension) to be used if the file exists
    \def\fodname{#1}%
    \def\dummyfig{commands/dummy}%
    % Check if output is PS (.EPS) or PDF (.JPG/.PDF/.PNG/...) figures
    \ifx\pdfoutput\undefined%
        % EPS figures only
        \IfFileExists{\fodname.eps}{}{\def\fodname{\dummyfig}}%
    \else%
        % Check existence of various extensions: PDF, TIF, TIFF, JPG, JPEG, PNG, MPS
        \def\figtest{0}% flag below compared to this value
        \IfFileExists{\fodname.pdf}{\def\figfilenamefound{1}}{\def\figfilenamefound{0}}%
        \IfFileExists{\fodname.jpg}{\def\figfilenamefound{1}}{}%
        \IfFileExists{\fodname.png}{\def\figfilenamefound{1}}{}%
        % and so on...
        % If no files found matching the filename (flag is 0) then use the dummy figure
        \ifx\figfilenamefound\figtest%
            \def\fodname{\dummyfig}%
        \fi%
    \fi%
    % 'return' the filename
    \fodname%
}%

Alternatively, here’s a much simpler version which seems to have similar problems:

\newcommand{\figFileOrDummy}[1]{%
    \def\dummyfig{commands/dummy}%
    \dummyfig%
}

The \def commands seems to be processed after the expansion of the macro they’re trying to define, so it ends up being \def {commands/dummy}... (note the space after \def) and obviously complains.

Also it seems to treat the literal contents of the macro as the filename for \includegraphics, rather than resolving/expanding it first, so complains that the file '\def {commands/dummy}... .png' doesn’t exist..

I’ve tried also doing something like
\edef\figfilename{\figFileOrDummy{\chapdir/figures/fluxcapacitor}} to try to force it to make \figfilename hold just the value rather than the full macro, but I get an Undefined control sequence error complaining the variables I’m trying to \def in the \figFileOrDummy macro are undefined.

So my question is either

1. How do I make this macro expand properly?; or
2. If this is the wrong way of structuring my macros, how should I actually structure such a macro, in order to be able to insert dummy/real figures automatically?; or
3. Is there a package that already handles this type of thing nicely that I’ve overlooked?

I feel like I’m missing something pretty fundamental here…

Answer 1

I think the point is that \expandafter is only interested in its arguments as a string representing a filename, so doesn’t evaluate it — macro languages are lazy! Try \expandafter {\includegraphics[width=8cm]}{\chapdir/figures/fluxcapacitor}.

Two points of style:

1. You don’t need to put % at the end of a line to stop spurious whitespace if the line ends with a control sequence: the control sequence gobbles up all following whitespace, including the end of line. This makes the code much more readable, to my taste. Note that, in particular, to Tex’s “mouth” both \def\newcs{abc} and \def \newcs {abc} are identical: they are exactly the same sequence of tokens.
2. I dropped the code around \figtest: you get better error reporting -always at a premium with Tex- if you use either \newif primitive (create new test with \newif\figexists, set/reset with \figexiststrue, \figexistsfalse, and test with \iffigexists…) or the Latex ifthenelse package (to keep with orthodoxy).

Cleaned-up code

I first thought the problem lay elsewhere, so wrote something prettier:

\def\dummypath{commands/dummy}%
\ifx\pdfoutput\undefined
\def\figFileOrDummy#1{\IfFileExists
    {#1.eps}{#1}\dummypath}
\else
\def\figFileOrDummy#1{\IfFileExists
    {#1.pdf}{#1}{\IfFileExists
      {#1.jpg}{#1}{\IfFileExists
        {#1.png}{#1}\dummypath}}} %or have more graphics types, if you like.
\fi