Not Enough Horse Power

[redpigg]

I was having a problem with the computer not consistently recognizing mouse
clicks.

Reading your posts you talk about screen definition and using the keyboard.

I have more computers nocking around the place than you can poke a stick at,and the ones that were misbehaving were the P111 types, the P4s and
the celerons were ok.

Perhaps the people who are having problems with bouncing boxes/mouse
pointers are trying to use an overloaded/underpowered computer.


redpigg

[forumsupport]

Hello,

The mouse clicks are dependant on window size, position and screen resolution. So, what we suggest is, keep the window in one size and position where you want to when you enter any keystroke/mouse actions in it so that when the task is run again, it will be in the same size and position as it was at the time it was created.

If the screen resolutions are different for the machines then the mouse clicks may not work. However, they can easily be edited using the Task Editor. What you can do is, edit mouse click by double clicking, and click on ‘Advanced View’ button. From ‘Relative to’ option, select ‘Window’ option. In the 'Relative To' option, the 'window' option is helpful if you are working in different screen resolutions but the location of the click remains same with respect to the window. Repeat this for all the mouse clicks in question.
Please let us know if that fixes the problem.

We suggest you to put delay after every action in task so that each action can get enough time to execute and task can run flawlessly. Insufficient delay can skip any command in task and results into task failure.

Hope that helps.

[philkryder]

The delays are vital.

you also should to build "spin loops" that wait for windows to appear.

Don't give up on the product.

It is very powerful, but you need to learn to avoid certain things.
And, to religiously USE certain things.

Use KEYSTROKES rather than MOUSE CLICKs if you can.

Use RELATIVE to WINDOW rather than screen (I think the default should be changed).

Pass and store variables in TEXT FILES - it is very fast to read and write files, and the file values can help you debug.

Learn to turn of the "delay" radio button in the editor.
It will make the code much easier to read, but DO keep the delays in between "action" lines.

I use a VARIABLE delays so that I can WATCH the results run (set to 1500 ms) - then I change it to 50 when I am done debugging.


Log to an OPEN notepad so that you can see where you are in the code WITHOUT running the debugger. the debugger is - a little buggy.

So if you are getting inconsistent results, turn off the debugger - or better yet run without the editor being open.

Save often.

Copy entire folders like
MY TASKS
to archive folders like
20008 06 02 at 15:32 my tasks
It is easy to screw things up.
Unfortunately, the syntax doesn't allow you to change code to a comment by just inserting a Quote or a <! - so save often.


Stick with it.
Phil

[NealO]

"Unfortunately, the syntax doesn't allow you to change code to a comment by just inserting a Quote or a <! - so save often."

But right clicking on a line enables you to enable/disable which has a similar effect and is not too painful.

Keep posting Phil, your info is always useful, thanks.

Neal

[philkryder]

Originally Posted by NealO

"Unfortunately, the syntax doesn't allow you to change code to a comment by just inserting a Quote or a <! - so save often."

But right clicking on a line enables you to enable/disable which has a similar effect and is not too painful.

Keep posting Phil, your info is always useful, thanks.

Neal

Thank you!
I'll give it a try.

There is just SO much to the product -it's a lot to learn.

I just wish that it had more in common with things like VB...