Image caching not releasing images in 7.0.7 (rc2)

Richard Maring maring.richard at gmail.com
Sun Jan 18 20:42:28 EST 2015


SOLVED!!

Found that I had an image holder in another card in another stack that held
the same source file name as the one that was not being released.  Set it
to "" and the refresh in the other stack started working again.

Even though the other stack was closed, the image cache still new it was
there and would not release the image until it was removed.

Lesson learned.  You must eliminate every reference to an image, no matter
where it is, in order for the cash to release it.

Rich


*Richard B. Maring*

Mobile:  (830) 928-7013

maring.richard at gmail.com



This email message and any attachments are confidential and may be
privileged. If you are not the intended recipient, please notify Richard
Maring immediately by replying to this message and destroying all copies of
this message and any attachments. Thank you.

On Sun, Jan 18, 2015 at 3:39 PM, Richard Maring <maring.richard at gmail.com>
wrote:

> Staring at code so long 1's look like 7's.......
>
> Sent from my iPhone
>
> > On Jan 18, 2015, at 2:35 PM, Richmond <richmondmathewson at gmail.com>
> wrote:
> >
> >> On 18/01/15 21:38, Richard Maring wrote:
> >> Hi,
> >>
> >> The following is built on Windows 8.
> >>
> >> I have a referenced image in an image holder that the user can click a
> >> 'Delete' button that deletes the image from the hard drive.  The user
> can
> >> then click a button to select a different image from their hard drive to
> >> display in the same image holder.
> >>
> >> The app takes the new image and scales it down and renames it to the
> same
> >> name as the previous image.
> >>
> >> When the new image is brought in the old image is the one displayed,
> even
> >> though the image source points to the newly created image.
> >>
> >> Obviously the new image cache is not releasing the old image and is
> >> displaying the prior cached image.  I have searched for any answers and
> the
> >> only thing I could find was from may of 2014.  The answer back then was
> to
> >> set the source of the image to something bogus and then set it to the
> newly
> >> created image.
> >>
> >> This does not work in LC 7.0.1   I have tried everything I can think of,
> >> including deleting the image holder and creating a new on on the fly.
> As
> >> long as the new file-name matches the old cached one, the cache won't
> >> release the old one.  You literally have to exit the app and come back
> in
> >> for this to change.
> >>
> >> It would seem there would have to be a way to clear the image cache or
> to
> >> tell LC NOT to cash the image in the first place.
> >>
> >> Any thoughts or ideas would be immensely appreciated.
> >>
> >> Rich
> >> _______________________________________________
> >
> > 7.0.7 (rc2)
> >
> > Wow: you are so far ahead it's beautiful!
> >
> > Richmond.
> >
> >
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>



More information about the Use-livecode mailing list