-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timeout for calls blocked by modal windows? #8
Comments
By now I don't know how it can be done. And, secondary, timeout may cause problems in case of long operations with large amounts of data. |
As to how, I'm not much help. I assume it might be better exposed via RDCOM? But for the long processing, I agree that it should not be turned on by default. If someone has a timeout that's too short, they did it to themselves. So that part does not bother me. |
Not sure if this is useful, but here are some links about dealing with modal windows & prompts. |
Thank you for the links. I will read them. |
Having not played with it, I'd guess that would leave excel in a hung state as well. The current call would return, but with no/bad data, and no way to get back in excel. (short of a system() call to kill the excel process.) |
If I cause excel to pop up a question dialog box, excel.link calls hang until I dismiss that excel window.
Would it be possible to add a timeout to these calls? I know I'd have to catch the error, but that's better than a hung connection.
(I'm using excel & rserve for remote access to data in excel workbooks. so there may not be anyone at the screen to click on the dialog box.)
The text was updated successfully, but these errors were encountered: