BloomTestsThatAvoidTheSetupFixture.PdfMakerTests.RunMakePdf C# (CSharp) Method

RunMakePdf() public method

Runs PdfMaker.MakePdf() with the desired arguments. Note that the implementation (as of March 2015) uses an external program to generate the PDF from the HTML file, so it doesn't need to be run on a background thread. The process includes a (possibly overgenerous) timeout, so we don't try to impose one here.
Running this on a background thread would be okay, except that on Linux, the interaction between Mono and NUnit and the Bloom method result in the BackgroundWorker.RunWorkerCompleted event never being fired if tests other than those in this file are run along with these tests. This is almost certainly an obscure bug in Mono. Running the method directly as we do here sidesteps that problem. (See https://jira.sil.org/browse/BL-831.)
public RunMakePdf ( PdfMaker maker, string input, string output, string paperSize, bool landscape, bool saveMemoryMode, bool rightToLeft, PublishModel layout, PublishModel portion ) : void
maker Bloom.Publish.PdfMaker
input string
output string
paperSize string
landscape bool
saveMemoryMode bool
rightToLeft bool
layout Bloom.Publish.PublishModel
portion Bloom.Publish.PublishModel
return void
		void RunMakePdf(PdfMaker maker, string input, string output, string paperSize, bool landscape, bool saveMemoryMode, bool rightToLeft,
			PublishModel.BookletLayoutMethod layout, PublishModel.BookletPortions portion)
		{
			// Passing in a DoWorkEventArgs object prevents a possible exception being thrown.  Which may not
			// really matter much in the test situation since NUnit would catch the exception.  But I'd rather
			// have a nice test failure message than an unexpected exception caught message.
			var eventArgs = new DoWorkEventArgs(null);
			maker.MakePdf(input, output, paperSize, landscape, saveMemoryMode, rightToLeft, layout, portion, null, eventArgs, null);
		}
	}