Comment 4 for bug 1463406

This is a known issue in wxWidgets 3.0.2 that didn't exist in 3.0.1. Of course there are other known bugs in 3.0.1 so you get pick which bugs you find the most irritating and use the appropriate version of wxWidgets. I've also check out the trunk of wxWidgets and the problem still exists. I looked at the wxWidgets changes between 3.0.1 and 3.0.2 and I didn't see anything in the wxPrintDC code that would cause this issue. I keep a 3.0.1 version of wxWidgets just for this purpose. Maybe some day I'll get motivated enough to figure out what changed so I can fix it. It's definitely specific to windows because on Linux the problem doesn't exist.