Browser window gets locked
Posted: Fri Nov 18, 2011 7:38 pm
Hi,
I use Helium scraper version 2.2.5.0, windows 7 x64, IE9.
I'm almost blocked by the following issue, from a practical standpoint.
After running any kind of project, the browser window gets locked, meaning that the lock symbol appears on the tab at the top of the window (as usual), and I cannot do any selection anymore nor interact in any way with the browser window.
I have to exit Helium scraper and run it again.
Besides this, everything seems to work properly, meaning that the extraction is performed normally, just the browser gets locked.
I've tried to look on the forum, but I could not find any similar bug report.
I have attached my project, real simple as you can see. BTW, it does not work properly, but this is not the problem.
I have noticed that when interrupting the execution by pressing the stop button, run it again, stop it again, the problem appears immediately after the second stop action.
Note : I let the program run until the first extract data command each time. Don't know if it matters, maybe the extract function is not involved at all.
Hope this is clear enough, and that you can reproduce the case on your side.
Please help !
Best regards.
I use Helium scraper version 2.2.5.0, windows 7 x64, IE9.
I'm almost blocked by the following issue, from a practical standpoint.
After running any kind of project, the browser window gets locked, meaning that the lock symbol appears on the tab at the top of the window (as usual), and I cannot do any selection anymore nor interact in any way with the browser window.
I have to exit Helium scraper and run it again.
Besides this, everything seems to work properly, meaning that the extraction is performed normally, just the browser gets locked.
I've tried to look on the forum, but I could not find any similar bug report.
I have attached my project, real simple as you can see. BTW, it does not work properly, but this is not the problem.
I have noticed that when interrupting the execution by pressing the stop button, run it again, stop it again, the problem appears immediately after the second stop action.
Note : I let the program run until the first extract data command each time. Don't know if it matters, maybe the extract function is not involved at all.
Hope this is clear enough, and that you can reproduce the case on your side.
Please help !
Best regards.