> On Sep 1, 2024, at 2:00 PM, Kenneth R Sloan <[email protected]> wrote: > > Yes - but what is the use case for > > Calibration c = new Calibration(imp);
This constructor is not needed. I have marked it as “Obsolete”. -wayne > When imp has an existing Calibration? > > My intuition was wrong and I’m trying to understand why this does what it > does. > > -Kenneth Sloan > > > On Sun, Sep 1, 2024 at 11:56 Wayne Rasband <[email protected]> wrote: > >>> On Aug 31, 2024, at 5:41 PM, Kenneth Sloan <[email protected]> >> wrote: >>> >>> I’m still learning the ins and outs of using Calibration. >>> >>> Today, I was surprise to learn that (in Java): >>> >>> Calibration c = new Calibration(ipl); >>> >>> Does NOT populate the values of c with the values in the current >> Calibration for ipl. >> >> Use >> >> Calibration c = imp.getCalibration(); >> >> to get the calibration of the image ‘imp’. >> >> Use >> >> imp2.setCalibration(imp1.getCalibration()); >> >> to transfer the calibration from one image to another. >> >> -wayne >> >>> Instead, I needed: >>> >>> Calibration c = new Calibration(); >>> c = ipl.getCalibration(); >>> >>> Not a big deal - but I wonder if this is the expected behavior, and if >> so, why? -- ImageJ mailing list: http://imagej.nih.gov/ij/list.html
