To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=44883
------- Additional comments from [EMAIL PROTECTED] Wed Aug 1 18:40:12 +0000 2007 ------- How about while walking the file system (or the registry or whatever) you periodically check for keyboard activity, especially up-arrow, down-arrow, escape, control-c, break, etc. and if present, abort the search? An indication that the application is still alive and doing something is essential, but making a user wait two or more minutes because they happened to scroll down through options and hit "Java" instead of remembering to mouse over that selection is punitive, to say the least. Not only that, but without polling for Windoze events while searching for JVMs, the OS thinks the application is "non-responsive". A user who pulls up Task Manager can reasonably conclude that the program has suffered a terminal hang and restart it. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
