Strange behavior when using vb.net's background worker

Discussions and Tech Support related to using the iMacros Component for .NET in your applications.
Forum rules
iMacros EOL - Attention!

The renewal maintenance has officially ended for Progress iMacros effective November 20, 2023 and all versions of iMacros are now considered EOL (End-of-Life). The iMacros products will no longer be supported by Progress (aside from customer license issues), and these forums will also no longer be moderated from the Progress side.

Thank you again for your business and support.

Sincerely,
The Progress Team

Before asking a question or reporting an issue:
1. Please review the list of FAQ's.
2. Use the search box (at the top of each forum page) to see if a similar problem or question has already been addressed.
3. Try searching the iMacros Wiki - it contains the complete iMacros reference as well as plenty of samples and tutorials.
4. We can respond much faster to your posts if you include the following information: CLICK HERE FOR IMPORTANT INFORMATION TO INCLUDE IN YOUR POST
Post Reply
hexinx
Posts: 3
Joined: Sat Aug 01, 2015 12:08 pm

Strange behavior when using vb.net's background worker

Post by hexinx » Mon Aug 03, 2015 7:20 am

Hello,

I've been using iMacros component to scrape off text from sites. I recently decided to use the "Background worker" component in .net to handle the component's functioning so I can keep the UI responsive. But, this is causing the iim component to behave strangely, I'm not able to get the same result when I play macros when from inside the background worker's asynchronous running, It gives me a #EANX# when the same script works perfectly when used by a regular .play() macro call from outside the background worker.

Any idea why? Probably something related to threading which I don't understand...
Post Reply