During a FILE - SEARCH action (while the file search is actually happening at runtime) I discovered quite by accident that clicking CANCEL on the file search seems to cause the program to stop responding. (My FILE - SEARCH action includes the "Recurse custom directories" option, and during testing I absent-mindedly asked it to search C:, not realizing that I was asking it to search the entire drive!).
I searched the forum for this info, but found nothing. If this happens regularly I guess I need to warn users not to click CANCEL during a file search? Maybe this is an OS issue? Thanks very much.
I searched the forum for this info, but found nothing. If this happens regularly I guess I need to warn users not to click CANCEL during a file search? Maybe this is an OS issue? Thanks very much.
Comment