why does the delay in an applescript editor increase by itself?...***

Applescript with random numbers. You need to vary the return 3.

(*

It is easier to diagnose problems with debug information. I suggest adding log statements to your script to see what is going on. Here is an example.

Author: rccharles

For testing, run in the Script Editor.

1) Click on the Event Log tab to see the output from the log statement

2) Click on Run

*)

on run

-- let's get a random number between 1.5 and 3.5

set myRandom to 1.5 + (random number) * 2

log "myRandom = " & myRandom

-- Write a message into the event log.

log " --- Starting on " & ((current date) as string) & " --- "

delay myRandom

-- Write a message into the event log.

log " --- Starting on " & ((current date) as string) & " --- "

end run

AppleScript resources

Learn AppleScript: The Comprehensive Guide to Scripting and Automation on Mac OS X, Third Edition the book

AppleScript Language Guide pdf download the pdf file

Intro to applescript with sending an email
http://mac.appstorm.net/how-to/applescript/the-ultimate-beginners-guide-to-apple script/

Every reply tries to remedy the specific bot-needs of the poster but nobody has yet answered the real question?

Why do the delay commands start adding up?

I have exactly the same problem in every script I write.

I want to process multiple files so I use a repeat function (repeat with aFile in theFiles .... end repeat)

In the repeat function I need the script to wait for some time

So i use a delay p.ex. delay 1

The scripts work, but you notice the delay getting bigger and bigger ...

And they don't just seem to add up, it almost seems to be exponential ...

No problem for 10 files but when I want to process 100 + files it is a nightmare

Does anybody have a clue ?

That doesn't happen with simple scripts that use the delay command, so it must be something specific to what you're doing. If I had to guess (which I do, since I can't see your script) I'd say it was an issue with using the Finder. The Finder's applescript implementation is buggy and prone to unexplainable slow-downs and delays. Try converting your script to use System Events if possible; see if that helps.

Thanks for the advice,

for now I have given up on the specific script and used other techniques.

Was a script to open illustrator files, outline fonts, outline paths, ... save them as pdf files and combining them in Acrobat pro, and mailing them to workstation.

too long to show all here, but the delays were to be found in system-events tell blocks like this:

tell application "System Events"

keystroke "g" using {shift down, command down}

delay 0.1

keystroke "v" using {command down}

delay 0.1

keystroke return

set the clipboard to newName & theExtension

delay 0.1

keystroke "v" using {command down}

delay 0.1

keystroke return

delay 1

keystroke "w" using {command down}

end tell

pittty I can not select Applescript in the Syntax Highlighting in this editor on this apple website ... :-(

anyhow, if ever one finds the actual cause I would be glad to know ... :-)

It's hard to address a problem neither one of us can currently replicate. 😝 I'll point out the one (very common) mistake you're making, in case it helps on principle. When you GUI script, keep in mind that System Events is a faceless background app (i.e., an app that lacks a GUI) so targeting it with GUI commands can be a foot-in-the-door for unexpected problems. If you're trying to manipulate Illustrator's GUI, then you should use something like:

tell application "System Events"

tell process "Illustrator"

-- put GUI scripting code here

end tell

end tell

That makes sure that the GUI-specific commands are going directly to the app that wants to receive them. It may not make a difference in most cases since SE will pass the commands on to the next app in line anyway, but it's purer code.