Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Triggers' "Repeat every" tends to repeat ad infinitum #583

Closed
jeanravin opened this Issue Nov 19, 2011 · 5 comments

Comments

Projects
None yet
4 participants

I don't really know how to reproduce it exactly but it happens often. I'm using custom iTunes volumes applescripts with cmd+optn+page_start (or page_end the two 45° arrows) and On Press›Repeat every 0.3s.

The scripts send growl notifications so the screen get flooded by them (and of course the volume tends to 0 or 100). It stops if I use another trigger (with insistence).

I don't have any problem when "Repeat every" is not checked so it shouldn't be my script's fault.

(10.6.8 & ß62)

Owner

skurfer commented May 4, 2012

Is this still a problem? I have the built-in iTunes volume controls set to repeat every 0.2s and they stop when I let go of the key.

I'll give it a try again and tell you.

I still have this issue.
But it's working fine with the built-in controls though.

Something with applescript maybe ?

Here is my script (needs a registered growl notification called Volume) :

tell application "System Events" to if (application processes whose name is "iTunes") is not {} then ¬
    tell application "iTunes"
        set sound volume to sound volume + 5
        my growl(sound volume as string)
    end tell


on growl(volume)


    tell application "System Events" to set isRunning to exists process "GrowlHelperApp"

    if isRunning then
        tell application id "com.Growl.GrowlHelperApp"
            notify with name "Volume" title "Volume +" description volume application name "iTunes"
        end tell
    end if
end growl
Owner

skurfer commented May 7, 2012

Something with applescript maybe ?

Maybe. Perhaps there’s such a delay before you can see the results of the trigger that by the time you let go of the keys, several events have been queued up and continue to run. I don’t have time to look at it now, but I’ll leave this issue open.

This is still an issue for me. It only seems to affect Run Applescript-type actions—either (AppleScript file) -> Run, or 'applescript text' -> Run as Applescript. osascript -e "applescript text" -> Run Command in Shell works fine, but is silly and slow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment