A common use case of this tool is for new users to run the pack unpack/scripts directly. When they do that currently, a window flashes open and then closes quickly. They often interpret this as something going wrong and go to get support, only to be told that that's normal.
Instead, add a prompt that waits for a key to be pressed before exiting after the tool finishes processing files.
If you wanted to maintain backwards compatible behavior when running the executable directly, you could add a flag to the executable that configures whether to wait or not, set it be false by default, and update the {pack,unpack}.{bat,command,sh} scripts to set it to true.
A common use case of this tool is for new users to run the pack unpack/scripts directly. When they do that currently, a window flashes open and then closes quickly. They often interpret this as something going wrong and go to get support, only to be told that that's normal.
Instead, add a prompt that waits for a key to be pressed before exiting after the tool finishes processing files.
If you wanted to maintain backwards compatible behavior when running the executable directly, you could add a flag to the executable that configures whether to wait or not, set it be false by default, and update the
{pack,unpack}.{bat,command,sh}
scripts to set it to true.