??V6 fix status??

[philkryder]

ForumSupport -

Can you give us any status on any of the reported problems with V6.

Here is a list that I opened during the beta period:

1) when using mouse click relative to WINDOW the click does not use X Y variables..
This seems to work if you use ACTIVE WINDOW
or
RELATIVE to SCREEN
or
omit the use of variables,
but,
when you use a wild card named window,
the X and Y variables appear not to be used.

Can you tell us where support is on fixing this issue?


1) multiple screens windows move and resize to primary monitor..
I noticed that one of the other users, Ryan H, had posted that he has problems with multiple screens.

As he notes this makes AA unstable
and
difficult to count on,
for solid production work.

I have been able to mitigate this problem "somewhat"
by using MOUSE CLICKS rather than controls.
And then running EXEs on a machine with only a single monitor AND using RELATIVE SCREEN with varibles and then adjusting the variables based on where the clicks occur.
If I get the variables from external files or Excel then I can change the click points without re-creating the EXE.

Is there any progress on fixing support for multiple monitors?

3) A maximized command window is still resized.
Again, this may only be with wild card windows.
I had a very simple ATMN that demonstrated the problem noted above with the X Y variables not working.
It also did a MAXIMIZE on a window.
But,
we noticed that the ATMN would RESIZE and move the window even though it used wildcards.

Any status on making AA stop causing wild card windows to be
resized and moved?


4) 120 dpi is an advanced XP desktop setting property.
It helps us older folk see the screens better by increasing the number of DPI in each character.

Unfortunately,
using 120 DPI cause the AA windows to not paint properly.
And,
worse yet, some mouse clicks are interpreted as being clicked on other controls than the one that is under the mouse.

Has anyone in support been able to look into the problem of using larger (120 dpi) font settings?


5) I use portrait mode when I edit.
With the fonts and screen resolution I use,
I can get about 55lines in a full screen editor.

When I duplicate or copy and paste a line,
that is showing in the MIDDLE of my screen,
the screen re-paints and the new line is
REPOSITIONED to the very BOTTOM of the screen?!

The repainting is annoying in itself,
but,
hen the REPOSITIONing further destroys the context and disrupts my concentration.

Has anyone at support been able to look into NOT repainting the screen
and
especially,
NOT REPOSITIONING the display so that a recently added line is at the bottom?
If you MUST repaint, the please leave the first line
that is displayed on the screen,
the same as it was BEFORE the repainting occurred.

6) F10 does not "single step/step over."
Fortunately,
ForumSupport was able to give a mitigation to use the "button" rather than F10.
But,
Often,
I don't want to disturb the mouse position.

Has Support been able to look into fixing F10, so that it runs just one line of code?


7) Save TASKS causes BREAK POINTS to be cleared.

This is totally counter intuitive.
There is a button to clear breakpoints if we want them cleared.
And,
If we try to RUN before saving,
we are FORCED to save,
WITHOUT clearing break points.

Why does saving by one method work differently than by another metod?

8) "Required" delays are often needed.
Often,
we will see recommendations to new folks to "add 200 ms delays" BEFORE or AFTER some commands to "improve reliability."
If those delays are needed,
please ask support to add them automatically
And not put them in the SOURCE listing to clutter it up.

If that is not possible,
can you at least give us a definitive list of what commands need the delays BEFORE them and which need delays AFTER them (if any).

The problems that lack of delays cause are VERY subtle,
and not easily distinguished from software bugs or coding errors.


I hope you can give us some positive news about the issues noted above.

Thanks for all your support.
Phil

[forumsupport]

Hello Phil,

We have already forwarded mentioned requests to the product development team and they would be implementing based on the priorities of various other features. But we will certainly let them know your view on the importance of these features.

Regarding the delay, generally Keystrokes and Mouse actions requires delay before and after the command.

Thank you for your feedback.

[philkryder]

Originally Posted by forumsupport

Hello Phil,

We have already forwarded mentioned requests to the product development team and they would be implementing based on the priorities of various other features. But we will certainly let them know your view on the importance of these features.

Regarding the delay, generally Keystrokes and Mouse actions requires delay before and after the command.

Thank you for your feedback.

does the amount of delay needed vary - such as with CPU speed or number of CPU engines- or is 200 ms always "safe."

[forumsupport]

Hello,

In our experience 200 ms works in most cases. However, the delay depends on how fast and well your application responds to the interactive actions like keystrokes and mouse clicks.

[philkryder]

are there any AA V6 patch updates available yet?

[philkryder]

here is the text of a simple ATMN that exhibits a problem when trying to do a mouse click relative to the WINDOW on my WINDOWS 7 LENOVO with twin engine pentium and office 2010 and 3 monitors.

If you change LINE 24 to be RELATIVE TO SCREEN, then it works just fine.


1 Comment: 185 lines 3 seconds to edit in 5.5
2 Comment: still under 3 second in v6
3 Comment: ================================================== ===========
4 Variable Operation : 200 To $Y$
5 Variable Operation : 50 To $X$
6 Variable Operation : 499 To $delayVariable$
7 Loop While Window Exists ("Microsoft Excel - ZZstarXYtest.xl*")
8 If Window Exists ("Microsoft Excel - ZZstarXYtest.xl*") Then (Wait up to 1 seconds - for Window to exist)
9 Close Window: "Microsoft Excel - ZZstarXYtest.xl*"
10 If Window Exists ("Microsoft Excel") Then (Wait up to 2 seconds - for Window to exist)
11 Keystrokes: [ALT DOWN]n[ALT UP] in "Microsoft Excel"
12 End If
13 End If
14 End Loop
15 Open "H:\My Documents\Automation Anywhere\Automation Anywhere\$TestDataIncludingXYgridEXCEL\ZZstarXYtes t.xlsx "
16 Delay: (5000 ms)
17 Maximize Window: "Microsoft Excel - ZZstarXYtest.xl*"
18 Delay: (1000 ms)
19 Start Loop "50" Times
20 Variable Operation : $Y$+30 To $Y$
21 Variable Operation : $X$+10 To $X$
22 Message Box: "x$X$ y$Y$ "
23 Delay: ($delayVariable$ ms)
24 Mouse Click: Left Button on 'x y variables relative WINDOW or SCREEN' in "Microsoft Excel - ZZstarXYtest.xl*"
25 Delay: ($delayVariable$ ms)
26 Keystrokes: '=X=$X$=Y=$Y$=##=$Counter$= in "Microsoft Excel - ZZstarXYtest.xl*"
27 Comment: why is the window zz* repositioned???
28 Delay: ($delayVariable$ ms)
29 Variable Operation : $delayVariable$ To $delayVariable$
30 End Loop
31 Delay: (1500 ms)
32 Comment: ================================================== ===========
33 Comment: ================================================== ===========

[philkryder]

philkryder asks:

?? Now that v610 beta is available,
can you tell us which of the problems identified in this thread have been corrected??

Thanks
Phil

[forumstaff]

Hello Phil,

Currently we are finalizing the list of Issues and Enhancements which are going to be taken care in the releasing version. We will be posting the list of issues fixed along with the list of enhancements very soon.

We thank you for your patience.