x
Please log in with password to access chatbox.
Index | Back | Reply | New Topic
Ideas
| Automation IP check delay | |
| 2009-01-09 16:53 | des43t | Uto, right now while running automation, the exchange waits a fixed 60 seconds before trying to detect whether the IP address has changed. I can think of instances in which it would be useful for the user to be able to set the amount of time before detection occurs. For instance, my IP address changes very quickly, maybe 5-10 seconds after the command is sent. On the other hand, sometimes I might like to be able to run a different automated script in the pause before the exchange starts up again, so it might be handy to be able to ask it to wait maybe 2 minutes before checking and restarting. Do you think a field could be put into the options for us to set this wait-time for ourselves?
Thanks, Des |
| 2009-01-09 17:37 | utopia.lv | Currently I am thinking of reducing wait time from 60 seconds to 15 seconds for the first IP change check.
In your case, if run unattended, the most flexible solution would be for script to kill Firefox, change ip address, do the stuff and start Firefox again. |
| 2009-01-12 17:27 | des43t | Problem is, I can't use a firefox restart as part of my automation, because that's when I sometimes get the "extension not found" error message, and then everything just sits there... |
| 2009-01-12 18:55 | utopia.lv | You will not get "extension not found" if Firefox is launched using the following shortcut:
firefox.exe -p Supermode -no-remote -url "http://utopia.lv/exchange/?do=supermode" "-p Supermode" is for launching Firefox with Supermode profile. I use separate profile for web browsing, development and Supermode automation. "-no-remote" is to allow several Firefox instances run at the same time. |
| 2009-01-13 03:47 | des43t | Thanks, I'll give it a try later this week.
Des |
| 2009-09-27 05:36 | LibertyMans-Bell | Mine takes 30 seconds. |