Is something like this feasible?
When using BTM,
[x] Skip File Operations that need user-input.
While the BTM is processing,
--- Skipped actions (that need user-input) are added to the Skipped List
--- When the user pauses the BTM, They Should:
- Clearly know that some file transfers were skipped.
- Be able to see which file transfers were skipped.
- Be able to interact with the skipped file transfers in the same manner as pending file transfers.
A: The first item in the BTM list, might be "Skipped Transfers", it could be red with a yellow background
B: If the user clicks on (or Enter?) the "Skipped Transfers", the list would scroll down to near the end, where the slightly-grayed-out-and-italicized "Skipped Transfers" live.
C: The user would interact with these items the same as other items in the BTM list.
If the user doesn't interact with the Skipped Transfers, (c.f. moving them into the pending transfers list), then they would be prompted for input after
any pending transfers are done.
The Skipped Transfers list, could also contain any file transfers that failed - they might be red and italicized instead of dim/grey/italicized.
*BLINK* TC9 Added WM_COPYDATA and WM_USER queries for scripting.