AMS locks files

[clueless]

Im making an animation editor at the moment the program splits an AVI file up into frames inside a directory it creates in the_TempFolder, the directory is then scanned for files and the filenames of the split frames are displayed in a list box.When it comes to editing the fames im haveing a few problems. Sometimes im able to change the BMP's stored there but other times AMS locks all the files stoping me from deleting them.
Does anyone know why this happens? Is this a bug?

[Darryl]

It's really tough to say at this point what is happening without seeing further details of its implementation. Something is holding onto those files.

Are you using AMS features solely for the project, or are you also using some third party technology? If it's mainly AMS stuff, it will make it easier to debug on our side.

If you can get together a sample project that our support department can replicate on our side, we may be able to get to the bottom of it. I think going through support would be the best course of action for this one.

[bule]

Try using Unlocker to see the locks on the file while AMS is running...

[clueless]

Thanks , i tried the unlocker ans it said AMS had hold of the files. I think this has more to do with the Image.dll i was using to manipulate the image rather than an error in AMS. I wrote a commandline prog to do the same job as the dll and the files are no longer locked.

[sside]

Thanks , i tried the unlocker ans it said AMS had hold of the files. I think this has more to do with the Image.dll i was using to manipulate the image rather than an error in AMS. I wrote a commandline prog to do the same job as the dll and the files are no longer locked.

I understand that you are using the Image.dll, one of my previous works that i have posted in this forum.
I also understand that you think that Image.dll may keep the image files it creates locked (even after you call the function that creates/manipulates the image file).

If that be the case i have the following to share with you:

I just run a test of the Image.dll as part of Image.v.1.0.0.7.apz that i have posted in this forum. I tested all the functions that create/manipulate image files and in all occassions, just after the dll call, i was able to delete the created image files (they are created in temp folder by the way).

If you are in able to show me where the Image.dll is locking the files, then show it. Other than that, it will be hard for me to tell.

However it is good to know that you have solved your problem.

And now maybe it is the time to share the work of your hand the same as i did.

With Kind Regards
sside

[sside]

Thanks , i tried the unlocker ans it said AMS had hold of the files. I think this has more to do with the Image.dll i was using to manipulate the image rather than an error in AMS. I wrote a commandline prog to do the same job as the dll and the files are no longer locked.

I was in able to replicate the problem when the source file was being locked. In my previous post i described the test i did with final image files which were not being locked.

If you take a look in the end of the webpage at Similar Threads you will see that the first post on the row is another post of yours with the same subject. Not clear was for me if you are refering at the Image.dll and Avi.dll, however from there i got the idea of the source file being locked. I did the test and it was so.

It is fixed now.

One suggestion i had though, those things (bugs etc) is better to be reported at the proper thread, in this case at Image Library thread, so i can keep track of these things and eventually fix them.

With Kind Regards
sside

[clueless]

sure but at the time i had no idea it was down to the dll. Theres no point me posting a command line program to resize pics when you've posted a perfectly good dll that does the job