06-28-2015, 05:58 PM
With my current code, I do not have this problem. I did fix a few bugs related to this, but I had thought they were caused by the new PDF library I'm using (which may not be true). My hope is that, due to the fact that I can't reproduce this with the new PDF rendering library and my implementation around it, that you won't experience if it after the next update.
Mike
Mike