#2239 Suggestion for warning on large drag-and-drop extraction using TEMP, intentional duplicate [pun intended!]

[A Person]

There's a well known issue mentioned in FAQ caused by Windows Explorer, such that extracting files using drag-and-drop requires the usage of a TEMP folder (on C:\ by default), duplicating the effort and itermediate space usage, just the way I just duplicated issues like:
https://sourceforge.net/p/sevenzip/discussion/45797/thread/145eff88/
https://sourceforge.net/p/sevenzip/bugs/699/
https://sourceforge.net/p/sevenzip/bugs/1320/
https://sourceforge.net/p/sevenzip/bugs/1537/

My suggestion is that there should be a compromise based on file sizes of either the extracted files, or the archive itself, and once they exceed a certain threshold, there should be a visible UI warning confirmation dialogue, informing the users about this fact (such that files will get extracted elsewhere before getting moved, and that it can be prevented by extracting directly).

• [I wonder if you really disagree with my view that 7zip is a de-facto standard default tool for majority of users, usually installed automatically (e.g. ninite.com), and thus it doesn't make sense to expect them to read through FAQ specifics for intuitive features. Do you consider this to be a niche tool? But even if you do, you could at least prevent the crash at 90% of a 5-hour progress as long as it's primitively easy to prevent due to the deterministic nature of disk capacity and environment variables.]

If nothing else, there should be at least an automatical check of empty space on the TEMP drive, such that the user will get warned about the likely risk of his process getting interrupted half-way, e.g. if their empty space is 10GB and the archive has 50GB. Note that I could state this requirement even in an alternative form of "'There is not enough space on the disk' should support a retry action, and display specific details of both the extraction path (drive), and the reason why this happened (along how much space is still required)". Nevertheless, imo the issue should be explicitly explained by default whenever a file is large enough (several GB?), or at least when the TEMP drive differs from the archive drive, due to the guaranteed duplication of the effort. Of course, a simple "don't remind again" checkbox should be obvious - and if this needs to be even more user friendly, the dialogue could even close itself in a few seconds and continue by default. (Basically, UX of the current extraction window with its mention of exclusive relative path sucks.) If you refuse the idea in spite of all that, you could at least just add a small warning to the corner of the extraction window if it's launched from drag-and-drop, hyperlinking to the FAQ or something :)

[A Person]

Damn, I forgot about this once again and caused my Explorer to crash by clicking on task-bar while it was not responding due to having no empty space on C:. Just because you "know" about a bug, it doesn't automatically make you avoid it. :( Brains of some people don't have a feature to set up custom script hooks on actions like drag-and-drop, so please, don't make it a dependency of the product :P