** Using WeBWorK **

When I look at your sample pdf I can also see the images being layered quickly. I can't see that on the DVI files on my machine.

(Note, if you obtain the DVI files via the download mechanism the images are not included in the download, and the images' addresses referred to in the tex and dvi code are unlikely to be correct -- thus I do not expect to see the images at all in the DVI download.)

Here is a debugging technique which may help. At the very top of the file cgi/cgi-scripts/welcomeAction.pl there is the following line:

$debugON = 0;

change this to

$debugON = 1;

this means that the intermediate files created when producing hard copy are not erased. (See the subroutine cleanup_downloadPS near the end of the welcomeAction.pl file:)

Here is the relevant code where $tempTexFileBaseName is defined as "${tempDirectory}Temp_downloadAllSets_$User";

	sub cleanup_downloadPS {
	 .......
                 unless ($debugON) {
	                unlink(
	                	"$tempTexFileBaseName.dvi",
	                	"$tempTexFileBaseName.ps",
	                	"$tempTexFileBaseName.pdf",
		            	"$tempTexFileBaseName.log",
		            	"$tempTexFileBaseName.aux",
		            	"$tempTexFileBaseName.tex"
		            ); 
                 } 
	}

Now attempt to download the hardcopy of set0; then inspect these files stored in the temp directory ($tempDirectory is defined either in Global.pm or possibly redefined in webworkCourse.ph )

Is the tex file well formed and are the addresses of the images correct? if so rename the file temporarily and run tex on it. Does this produce a postscript file? can you view the postscript file with images? Is it the same as the postscript file that already exists? If the postscript file is fine, convert the file to pdf and see if that works.

The command line commands used by WeBWorK to convert from tex to dvi to ps to pdf are given at the top of the subroutine prepareHardCopy in welcomeAction.pl.

Hope this helps.

-- Mike

<| Post or View Comments |>