Are unsaved clips temporarily stored somewhere in case of an unexpected system glitch?

Hello to all Hyperionics users and doers,
 
I have been a very satisfied Hypersnap user for 12 years or so (v6), but I'm encountering a frustrating problem today (not with the utility itself), and this might be my first assistance request (can't entirely remember!). I am using Hypersnap v8.15.0 64 on Windows 10 64bit v1803.
 
A couple of hours ago, I went through a rather extensive clipping session and made the mistake of not saving the clips immediately.
 
A bit later, I experienced a system glitch, probably because of the FileBX Explorer add-on that I really need although it hasn't been updated for years. I got over it by Ctrl-Alt-Del after a while, but several applications had quit, among which Hypersnap.
 
So I'd rather not have to go through that clipping session again and am wondering if there's a temporary saving folder for the 01.jpg, 02.jpg, etc. somewhere.
 
Thanks in advance, and... let's keep on clipping!
 
Lionel

Thank you very much, Greg, for giving me a "same-day" reply that's clear and helpful -- and of course, it's always special to be taken care of by the author directly! (I would have liked to be able to "thumb it up" it at once, but I did catch a dialog that said "X    Rate Post" and that's OK, of course, + this is my more verbose workaround ;).
 
Upon reading your answer, I proceeded to enable auto-saving as you suggested, and was exposed, in doing so, to a number of features that I don't use -- we each develop a method for a task and tend to stick to it -- and was happy to be reminded about them.
 
Bonne après-midi et à bientôt -- thanks for that brilliantly maintained and indispensible tool and  keep up the good work!
 
 
Lionel
 
PS : Silly me, I had forgotten you were also the author of "File BX"! Isn't there a way to update this just as indispensible utility so that it doesn't freak out Win10 every now and then? (Off this topic, but couldn't resist!)

Thank you anew for this additional gracious answer, Greg.
 
"Code injection into other processes". Again, I really appreciate your simple and clear answers. This speaks clearly enough to me, for the simple reason that yesterday, during my "tour of the Hypersnap premises" that I don't visit often, ;) I took the time to read the whole explanation of why  "(TextSnap)" was not supported anymore, and now I understand that you used that same nifty strategy in both.
 
And as an occasional programmer (mostly in the 80s, though), I can both appreciate how something like that might have been tolerable then but is not now, several orders of complexity later... and how smart it is: why not, to do a task related to other applications, ask them nicely how they do it themselves and even make them work for us discreetly? :D
 
You may take this as not just one thumb up but many! :)
 
Amicalement et admirativement,
 
Lionel
 
[PS - It goes without saying but may be clearer with: in the same spirit as that of your decision to let "File Boxes Extender" remain publicly available in its latest version, I am very happy and I still gain a lot of times using it, occasional system confusion notwithstanding!] 

An thank you for your very harmonious and endearing conclusion of this exchange, Greg, which I wrap up in the same kind of simple appreciation and sincere good wishes on what counts! :)
 
 
Lionel