hi,
here a little thing appened yesterday.
i have a lot of files with read-only property (what i did not know)
i added them into the batch process list
i started the process and off course it bugged track by track.
Then the whole .gw temp files remains after i closed goldwave . i have to delete the myself.
i guess it is easy for you to add a step-check to test read-only properties to alert the user of this problem....(specially when i checked 'overwrite existing files' option)
have a good day
Mike
little bug in 6.30 batch processing
-
- Posts: 167
- Joined: Sun Nov 28, 2010 6:07 am
- Location: Amiens
- Contact:
-
- Posts: 167
- Joined: Sun Nov 28, 2010 6:07 am
- Location: Amiens
- Contact:
Re: little bug in 6.30 batch processing
this bug remains in 6.31.... i felt on it !
Re: little bug in 6.30 batch processing
That's too bad. The effects bug I had in 6.30 went away in 6.31.
I don't want to read the manual either, but, then, it isn't my problem, is it?
-
- Posts: 167
- Joined: Sun Nov 28, 2010 6:07 am
- Location: Amiens
- Contact:
Re: little bug in 6.30 batch processing
thank for having fix that!
i'm glade it works now.
you can even improve the process by detect the read-only of files once we add them into the list, so before we launch the batch.
And maybe you can add a feature to auto change the read-only property (so we don't need to go back to explorer to change this option).
again, thanks, good job.
i'm glade it works now.
you can even improve the process by detect the read-only of files once we add them into the list, so before we launch the batch.
And maybe you can add a feature to auto change the read-only property (so we don't need to go back to explorer to change this option).
again, thanks, good job.