When you start a print job, the Graphic you want to print is added to a PrintRootFrame. When the Layout of your Graphical object is complete the Graphical object is printed. Not knowing about you particular Graphic hierarchy I cannot say much. It could be what Duke wrote is true. Or your layout is happening in cycles. For example, you have a code that makes the layout invalid after it was valid - E.g. you may have a code that computes some stuff and then has "after 0s do" and in it you are invalidatiing the layout - so another layout cycle kicks in. When you print, the PrintRootFrame does not know that the Graphical object it is printing is going to invalidate the layout soon and so should wait. It will just prints after the first layout cycle completes. If possible, could you send your code so that I may have a better answer and possibly a solution.

Thanks,

-Kamal

PS. I do not think that this applies to your case. But anyway I will mention it here. If you are printing a Graphic whoes draw method ends up drawing differntly every time it is called, you may notice that what you print is not what you see. The point again is that Print is like a "snapshot". Once the first layout cycle is complete after the Graphic is added to the PrintRootFrame, the first draw that will be called during printing is what you will see as being printed. If there are futher layouts and draw changes, they will not be reflected.