Exported Graphic Looks Different depending on DPI setting

When I attempt to export a graphic (a plot of data with annotations like tags), the image I see within Igor looks completely different from what is generated as a file (png/tiff) on my computer. The tag locations will have moved such that they are on top of each other, and even sometimes the axis scale changes. There also appears to be some variation of these locations depending on the dpi setting.

Although I have used Igor for many years on several computers, and I have never had this issue previously in creating publication quality images even when a journal requires a dpi setting of 600. Does anyone know if it's a screen resolution setting issue (such as a Windows 10 issue) or if there are steps I can take within Igor?

Thanks so much for your help.
A graphic window might export the layout of its objects differently depending on its settings and the export settings. A layout window will export the layout of objects in the graphic window consistently regardless of export settings. So, in answer to your question ...

mschulze wrote:

... or if there are steps I can take within Igor [to avoid the problem]?


Create the graphic, put in on a layout, and export the layout.

--
J. J. Weimer
Chemistry / Chemical & Materials Engineering, UAH
Try changing the size of the graph window and note if items stay in the correct location or if they move. Perhaps also select a zoom setting (right click in margin for a popup menu.)

I have seen people specify an annotation anchor location in, say, the right-bottom corner but then position the annotation in the upper margin. So, check if the anchor locations makes sense.

Also, please specify what version of Igor you are using.

Larry Hutchinson
WaveMetrics
support@WaveMetrics.com
The fundamental exported graph is simple and identical in both cases. Only the resolution settings changes alter the output in 'close call' situations (this makes sense, since the output routine is called for display and export individually).
My solution was simply 'use fixed settings'.
I tracked it and the last occurrence I could find was 6.38B01 (I don't have newer versions installed atm; not much to do and saving to buy IP7)
HJ