Unpredictable delete function

[BrianCee]

Yes - the Aftershot pro development team are visiting these posts in the Aftershot Pro forum - but if you have a specific wish why not add it to the "wishlist" - which is what the developers concentrate on - you can find that wishlist here :-
viewtopic.php?f=90&t=44903

[maggus]

I have the same bug - AfterShot deletes the wrong image, and its really ANNOYING!
Can anybody tell me if Corel is following these posts? Reading and actually considering them?
Because I tried contacting Corel over this - impossible, their forms on the website are a mockery, allegedly I didn't fill all the blanks... though the alleged blanks don't even exist on the form. User support really sucks...

I have quite a wish list for AfterShot Pro (cause I love it and I even more love to see it improved), any idea how one can make this known to Corel. To me they seem like a forteress impossible to penetrate....

Hi,

I often feel the same as you .... but have you ever tried bug reporting via "The Monkey" ? -- I already reported it, afx reported it, maybe you should also complain about this issue to raise its priority.
O.K., you do not get any feedback there and you can´t expect them to promise anything, but at least it should arrive at the developers (I hope). With little luck they´ll pick it up and fix it.

cheers
Markus

[nyukuri]

THANK YOU!
in the mean time I had already found the wish list my self and posted my hopes and dreams
the surveymonkey was new to me, but I am using it - Thanx again!

[cholmquist]

Gosh, this bug has caused me to lose many valuable files.
I am shocked about it, really. Deleting another file than the one selected is pure insanity.
If the tool is so confused about which file it's operating on, maybe it could at least add the name to the MessageBox (Are you sure to delete master file XYZ) so the user has a chance to see it.

Since devs usually are hopeless in reproducing bugs, here are the very complicated steps, with many clicks involved.

1) Select image A
2) Right click -> Send selected files to batch > (Some batch)
3) Select Image B (or use next/prev keyboard)
4) Hit delete and confirm
5) Image A is deleted.
6) Enjoy.

[nyukuri]

6) Enjoy.

+1

[RickHeath]

I think part of the problem is that ASP doesn't use a separate pipeline/engine for stuff it does on screen and in batches. I don't know if the problem is therefore easily solvable by the programmers.

Changing your workflow slightly can prevent/reduce the problem. I find ASP works best by making changes to all images then sending them to a batch (that is primarily what it is designed for - outputting multiple image) at the end of the editing. Similarly with deleting - although I should perhaps point out that I don't delete files within ASP as I use a separate DAM app - mark your deletes as you go along (with the "reject" flag perhaps) then filter, select & delete in one go (& not while the output batch is running!).

Regards

Rick.

[grubernd]

Gosh, this bug has caused me to lose many valuable files.

while the bug falls under "needs immediate fixing" i wonder why you lost many valuable files.
just because the delete-function should work is not an excuse to re-use it.

[cholmquist]

just because the delete-function should work is not an excuse to re-use it.

I can't parse that sentence, sorry.
Either way, I did not know until much later that delete did not do what I expected. I had a hunch that some images were gone that were not supposed to, but since I had batch processed and shipped to clients already I didn't investigate.
Then with some hobby pics I noticed clearly there were some issue and I tried to reproduce it, and found a way that works every time. This should be hotfixed asap imo, but well..

[cholmquist]

Changing your workflow slightly can prevent/reduce the problem.

Yes, that's what I have done now. But without knowing why files were gone I couldn't change my workflow.. I actually first thought it was one of my batch schemes that deleted the files randomly, that's where I started looking. Only after investigating I realized that batch + delete is the core of the problem.