Just to add a bit.
This is not limited to just CFimage. CF file functions and tags exhibit the
same behavior. Although, in my experience has been better with version 9+.
Seems like CF is a bit asynchronous with writing files. So a file write,
immediately followed by another file action like move
>> How can I program it to unlock as soon as it has been re sized or
cropped?
It depends on what is locking it. As a test maybe have CF immediately
resize another "test" image after re-sizing the target image and then see if
you can delete the target image.
Dennis Powers
UXB Internet - A websi
>no, you have to wait until cf has finished with the file, if you are trying
>to delete immediately afterwards then that is probably why.
>You should either try adding a delay, or simply add the images to a list
>and setup a scheduled task that comes and deletes the files in that list
>later on.
>
3 matches
Mail list logo
