Jump to content

Recommended Posts

  • 2 weeks later...
Posted

@razorfish228

There are a few differences, one of them being, the custom delay. The script created by my tool allows real time delay, not a preset of 100ms as with the given tool.

Secondly, My tool has a timeout on the window, which wait for a certain time for the window to be activated, and exits if it doesn't get active, while in case of the scriptwriter generated script, you might end up in a loop if there is something wrong with the window you were trying to open.

Thirdly, The ScriptWriter tool is available if you have the SciTE installed, but if you don't want to, then you can easily create and use the autoScripts on any computer, without having to install anything by just two .exe files (the autoit executable and my compiled script executable)

I know its not something really great and unachievable, but its just a little something I created and wanted to share with the rest you.

Cheers

Ankit

[topic="80940"] AutoScript Creator, Script to automate anything![/topic]

  • 7 months later...
Posted

Hey Ankit, .. nice tool there!...

Here's some more stuff that you can think about doing ..

- Provide a keyboard shotcut to start recording, rather than recording directly after the program is launched. Helps quite a bit in keeping the desktop ready. I know all this can be done before hand too, and the miniimal unwanted recordings can be stripped off the top part of the generated script. This is just an addition to improve things.

- print a $script_speed = 1 at the beginning of the generated script, and print all sleep times as Sleep (time * $script_speed). This way, the generated script can either be played slightly faster, or slightly slower overall.

- read a command line parameter after your EXE, for a debug output filename. this could become a variable in the script like $outputfile = "from command line". Initialize a counter within your program and increment when you print a WinWaitActive. Instead of calling Exit, call a function with this value such that the counter value is written to the file specified in the command line as the script exits. This way, if the generated script stops mid-way, the counter gives an indication on the progress of execution (very useful in long recordings where its hard to track what happened).

2 cents,

Praveen

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...