Ouch, I apologize for that.
Let me think for a second about how to handle that.
So what SC is doing is saving the file without objects so that you can edit it, but marking it as needing resaving in ScreenshotCaptor itself.
If you edit the now-objectless file in another program, SC will reload and reupdate it.
And if all goes expected, when you navigate away from the image in SC, it will prompt you to resave (or auto resave based on your options).
But if, as happened to you, you dont navigate away from the image in SC (or minimize SC window) and it hasnt had a chance to resave it, your image file will still be in a limbo state without objects drawn on it.
The dilemma is that Screenshot Captor doesn't *know* that you have stopped editing the program in a different program so it doesn't know how to ask you what you want to do after you've stopped. Possible solutions would be for SC to use a temporary file to send to your graphic editor and reload from THAT file after you finish editing it. That would make a bit more sense but has its own difficulties. It's such a rare function that I'm not sure it's worth the effort.
Another option would be to put up some bit reminder text on the bottom area or something, with a button to dismiss/save.