Thanks for this explanation. I work exclusively in Java and tend to prefer calling methods directly rather than using “equivalent” IJ.run versions. When I do, I always specify the image and never (well, hardly ever - and only when I forget) depend on the “active window” when I can avoid it.
waitTillActivated() is new to me - I’ll start using it after every show(). I guess I haven’t been bitten by a race condition recently, although I have dim memories of problems when dealing with keystrokes (my memory is too hazy for specifics). For my purposes, I suppose I really want an “all’s quiet” method that waits until all operations are complete. Inserting waits always feels problematic, since machine speeds can vary widely. Usually, I’m happy to wait for much longer than may be necessary, but that always feels kludgy. Grumble… —- Kenneth Sloan (von meinem iPhone13 gesendet) -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html
