01-19-2014, 07:03 AM
Finding accessible objects is slow. To make faster, try:
When creating code with dialog "Find accessible object", check "as firefox node". Also try to check "reverse". Test speed with the Test button.
Try other web browser (Internet Explorer, Firefox or Chrome). Will need to create code for each, same code will not work in all browsers.
Use Internet Explorer, and create code with dialog "Find html element". Test speed too. It also can wait.
Create code with dialog "Find image". Test speed too. It also can wait.
Maybe your macro is slow because newoffer clicks every 1 s. Maybe need to click more frequently. But look how much CPU it uses.
To relogin, don't know, maybe some trigger can be used, or the code changed somehow to look for a "relogin" object, maybe in separate thread (like now newoffer does), or newoffer could look for the object.
When creating code with dialog "Find accessible object", check "as firefox node". Also try to check "reverse". Test speed with the Test button.
Try other web browser (Internet Explorer, Firefox or Chrome). Will need to create code for each, same code will not work in all browsers.
Use Internet Explorer, and create code with dialog "Find html element". Test speed too. It also can wait.
Create code with dialog "Find image". Test speed too. It also can wait.
Maybe your macro is slow because newoffer clicks every 1 s. Maybe need to click more frequently. But look how much CPU it uses.
To relogin, don't know, maybe some trigger can be used, or the code changed somehow to look for a "relogin" object, maybe in separate thread (like now newoffer does), or newoffer could look for the object.