Thanks for the rapid reply. My current theory is that the overlay becomes invisible because of the downsizing done to fit the huge image on the screen. I’ll test this later today.
In the meantime, I implemented a “display” version of the huge image, keeping the original image hidden. It would be nice to have StrokeWidth specified in screen pixels, not shrinking (or expanding) as the image is scaled. but - this is probably not worth the trouble. My current scheme requires what I consider to be best practice: the plugin works in “world coordinates”, and converts to raw pixels only at the last minute. -Kenneth Sloan -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html
