Changes flag not always set after editing image

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Changes flag not always set after editing image

Ingo Bartholomaeus
Dear all,

In a macro I want to make sure that the currently active image is identical with the saved file, using the  is("changes") macro function. When testing, I found that some modifications to my RGB stack, like simply drawing using the pen tool, do not correctly set the changes flag to true. Can this be fixed somehow?

Thanks,
Ingo
Reply | Threaded
Open this post in threaded view
|

Re: Changes flag not always set after editing image

Rasband, Wayne (NIH/NIMH) [E]
On Jul 14, 2011, at 11:40 AM, Ingo Bartholomaeus wrote:

> Dear all,
>
> In a macro I want to make sure that the currently active image is identical with the saved file, using the  is("changes") macro function. When testing, I found that some modifications to my RGB stack, like simply drawing using the pen tool, do not correctly set the changes flag to true. Can this be fixed somehow?

This bug is fixed in the ImageJ 1.45l daily build.

-wayne
Reply | Threaded
Open this post in threaded view
|

Re: Changes flag not always set after editing image

Ingo Bartholomaeus
Dear all,

Many thanks to Wayne for quickly fixing this issue!
However now the changes flag is already set ' true' when I open any .avi file - without any modifications...

Ingo

-----Original Message-----
From: ImageJ Interest Group [mailto:[hidden email]] On Behalf Of Rasband, Wayne (NIH/NIMH) [E]
Sent: Thursday, July 14, 2011 11:35 PM
To: [hidden email]
Subject: Re: Changes flag not always set after editing image

On Jul 14, 2011, at 11:40 AM, Ingo Bartholomaeus wrote:

> Dear all,
>
> In a macro I want to make sure that the currently active image is identical with the saved file, using the  is("changes") macro function. When testing, I found that some modifications to my RGB stack, like simply drawing using the pen tool, do not correctly set the changes flag to true. Can this be fixed somehow?

This bug is fixed in the ImageJ 1.45l daily build.

-wayne