Abort macro and close all windows on error

[stefmit]

Is there any "all-encompassing" function, that would kill absolutely all open windows, and abort the running macro, until next time when it is scheduled, in case of a failure? I have been on and off with trying to develop a reliable macro for some Java apps, but the windows opening and closing seem to have alife of their own, not abiding by the same rules every time the macro runs. I abandoned last year any attempts, but now I am forced to go back and figure this out, and the failure of the macro "once in a while", on PC fully dedicated to running it, kills me

TIA,
Stef

[support]

Hi,

There is no function to close all open windows. Firstly there is no reliable way to do this as each application closes differently and handles close down messages differently. Also it is highly undesirable to close all open windows. Don't forget that there are many hidden applications and windows on your system. Killing them could have undesirable consequences.

Perhaps there's a different solution - perhaps you really want to close windows of just one particular application, or a known number of applications? Perhaps killing that particular process would suffice? Perhaps if you explain what you want to achieve we may be able to provide some solutions.

[stefmit]

Perhaps if you explain what you want to achieve we may be able to provide some solutions.

Thank you for answering - I may actually dare to take advantage of your kind offer, and explain to you what I am seeing, that fails my macro, and seek advice on how to fix, vs. killing processes all the time

WARNING - long!

First - the requirements: Java-based client application (a.k.a. Jinitiator), starting within a browser, then spawning processes which run within a "main" window, identifiable by "handle", as well as title, but which contains "sub"-windows (the terminology, of course, is made up), which are not identifiable. Unfortunately these "sub"-windows are the ones accepting user input. I need to develop a macro to provide various types of input into these "sub"-windows, which are actually front-end to database quries, via what Oracle calls "Forms server", then wait for results to be returned, and provide further input.

Second - the challenge: have tried various approaches for handling input, when due, with Wait>"value", WaitCursoChange>"value". Between these, I obviously have to wait for various results, then change "sub"-windows, and move onto other test steps, etc. I handle everything via keyboard input, to avoid the hassle of mouse cursor positioning, but even in such case the results are totally incosistent: sometimes the "sub"-window supposed to get the input does not show up fast enough, and the keystrokes open other menus, than hang the whole process ...

Having said all of the above, i s there something more I should consider, to control these types of environments? I have purchased the "pro" version of this software, to be able to build an executable, which I need to send to a remote site, which - from last year experience - proved to be even more of a disaster (PCs not fully identical respond even more inconsistent to the design).

Reading all the blurb above, I realize that it would be hard to describe an application, without actually seeing it, but I am hoping that some of these links (even the first should be revealing) would explain more of the challenge I am not able to address yet:

http://www.google.com/search?q=scripting+jinitiator

TIA,
Stef

[support]

Stef,

If you like, you can download a tool that allows you to initiate a connection for us to be able to view your machine and then you can show us exactly what the issue is. We may also be able to give some tips as to how to make the script more reliable.

If you are interested in arranging a remote support session please drop us a line on [email protected]