X10 Community Forum

🖥️ActiveHome Pro => Plug-ins => iWatchOut/iWitness => Topic started by: Tracy_X10 on June 26, 2009, 10:51:44 AM

Title: Cannot delete stills from iWatchout
Post by: Tracy_X10 on June 26, 2009, 10:51:44 AM

I noticed another post on this topic which was from 2006, so I'm assuming it's not fixed yet but......   I am unable to totally delete any images from iWatchout.  I can delete the image, which goes away from the folder, but there's still an image holder in its place within iWatchout.  I've tried deleting through the iWatchout application, and even deleting directly from the folder within Windows but the placeholder still remains.  Any idea when X10 is going to fix this within the application?   B:(

If anyone knows of a fix for this, I'm all ears!

Thanks

Title: Re: Cannot delete stills from iWatchout
Post by: Tuicemen on June 26, 2009, 11:06:03 AM

Try specifying a location for the files other then the default.
Your able to specify separate folders for video, auto stills and snapshots in tools/preferences
Then delete the default folder/s.
 >!

Title: Re: Cannot delete stills from iWatchout
Post by: Tracy_X10 on June 26, 2009, 11:47:36 AM

Thanks Tuicemen.  I'll give that a try and let you know.

Title: Re: Cannot delete stills from iWatchout
Post by: Tracy_X10 on June 26, 2009, 04:17:36 PM

Well, I created a new location on my E:\drive and deleted the original C:\drive folders which got rid of the placeholders from those days, but when I create new Stills and try to delete the, I'm back in the same boat.  In order to fix it, I have to delete the folder which has all of the stills for that day and the txt file which contains the timestamps.  I've tried disabling timestamp overlay, but that didn't do it either.  Oh well, guess this one is an annoying bug until X10 can fix it. Does X10 have a bug reporting process somewhere online?  Thanks.   B:(

Title: Re: Cannot delete stills from iWatchout
Post by: birdzeye on August 24, 2010, 08:02:05 PM

Actually, the reason it won't delete the stills, I've found, is because x10.nets is running. Go to windows task manager and turn off x10.nets.