"SET !POINTER NO" doesn't work in v6

Support for iMacros. The iMacros software is the unique solution for automating every activity inside a web browser, for data extraction and web testing.
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
whitertlnav
Posts: 43
Joined: Tue Mar 28, 2006 4:10 pm

"SET !POINTER NO" doesn't work in v6

Post by whitertlnav » Thu Aug 23, 2007 3:45 am

"SET !POINTER NO" doesn't work in v6 as it did in previous versions. Any explanation as to why this feature was disabled?
User avatar
Tech Support
Posts: 4948
Joined: Tue Sep 20, 2005 7:25 pm
Contact:

Post by Tech Support » Thu Aug 23, 2007 4:44 pm

We added this feature in the first place because the pointer was sometimes interfering with WINCLICK. With version 6, the new DirectScreen method no longer has this problem.

Is there a specific reason why you prefer to have this option back?
whitertlnav
Posts: 43
Joined: Tue Mar 28, 2006 4:10 pm

Post by whitertlnav » Thu Aug 23, 2007 5:25 pm

1. I have found in my experience that disabling the pointer uses less system resources, and my macros seem to run a bit faster.
2. I don't want to see those blue boxes when I'm running my macros.
3. Documentation still mentions that this feature is available.

Are there any other features that have been disabled in v6?
Post Reply