Delete issue
Often, and I haven't quite figured out the pattern, though it seems like it's the first time (or first times) I go into a new directory of captured images, when I go to delete an image I get a popup:
Some of the captures could not be moved to the specified destination due to insufficient space, permissions, or name conflicts.
And it won't let me delete the image. If I quite out and come back in, it will often let me do so.
This is using the \"Browse folders...\" button. I have plenty of disk space free (20 gig). There aren't any special permissions settings going on. It happens consistently on first time open of folders, though I haven't quite figured out what makes it go away (for instance, deleting the active collection and then returning to the folder does not fix it). Plenty of memory free (no paging going on) and as I mentioned earlier, goes away (at least sometimes) when you exit and return back in.
Hate to say it, but it seems like a bug. Searched the knowledge base and found no matches. This is running on XP SP2 with version 3.6.
Thanks.
Some of the captures could not be moved to the specified destination due to insufficient space, permissions, or name conflicts.
And it won't let me delete the image. If I quite out and come back in, it will often let me do so.
This is using the \"Browse folders...\" button. I have plenty of disk space free (20 gig). There aren't any special permissions settings going on. It happens consistently on first time open of folders, though I haven't quite figured out what makes it go away (for instance, deleting the active collection and then returning to the folder does not fix it). Plenty of memory free (no paging going on) and as I mentioned earlier, goes away (at least sometimes) when you exit and return back in.
Hate to say it, but it seems like a bug. Searched the knowledge base and found no matches. This is running on XP SP2 with version 3.6.
Thanks.
0
-
Weird thing I just found is I can delete one image earlier in the listing, but not another later in the listing. There are no other apps open accessing the file, at least that I know about. I'm pretty sure if I come in and out it will be deletable.
On a related note, I've also found that even when you close a capture session, externally you cannot delete files in the previously opened capture session until you close C1. Clearly C1 isn't closing files or something on a capture session close. This may be part of this issue - perhaps files aren't being closed in one section of code, which is preventing the other from doing the delete.0 -
This problem appears to be resolved in 3.7.
Thank you!0
Post is closed for comments.
Comments
2 comments