Solution to the issue "Queue.MergeAllJobs() leaves a job orphaned"

PDFCreator PDFCreator English
1

I have the same issue as described in the topic "Queue.MergeAllJobs () leaves a job orphaned" and I found the solution in the source code (pdfforge/PDFCreator). Tested on PDFCreator free v4.2.0.10.

The solution is in QueueAdapter.MergeAllJobs do "JobInfoQueue.Remove(nextJob);" before "_jobInfoManager.Merge(firstJob, nextJob);" (swap them).

The cause for the wrong behavior is that JobInfoManager.Merge set nextJob.InfFile to null (by calling DeleteInf), but JobInfoQueue.Remove expects InfFile to contain the real path. It is used as a key to remove from _jobFileSet. Null in the InfFile causes the real path hangs in _jobFileSet and prevents a job with the same path being added afterwards (in JobInfoQueue.Add).

If do "remove" before "merge" then "remove" will work on the real path in InfFile and everything seems to work.

I tested it by rebuilding "PDFCreator.ComImplementation.dll" and replacing it in the installation folder.

The same correction needs to be applied in QueueAdapter.MergeJobs too.

I am hopeful the solution will be in the release.

2

I would like to know are you planning to consider this solution?

I am waiting for your decision. If you do not fix this, I will look for other ways to merge pdf files.

Thank you.