It's not that simple, though, because that only works on Transmission. I meant a general version, which would have to "talk" to QS to get the currently selected object. Now, if the only app there's a problem with is Transmission, by all means do something simple like that and be done with it.
On Apr 18, 7:08 am, halbtuerke <[EMAIL PROTECTED]> wrote: > An ApppleScript for this kind of task is really simple: > > quit application "Transmission" > delay 5 > launch application "Transmission" > > The delay value is measured in seconds. > > Daniel schrieb: > > > I've had this problem as well, though for me it's fairly > > intermittent. I've also had QS simply refuse to show the relaunch > > action for an app that I know is open. I think you might be on the > > right track regarding QS trying to relaunch and app before it's > > finished closing. Might anyone be able to write a relaunch app > > applescript with a "pause .5" (or however long) or similar in it? I > > don't know how to write AppleScript actions for QS, unfortunately... > > > One question, also, for the QS devs: I've used the "relaunch" action > > on QS itself and had it work--how is that possible? And, if that > > works, might the problem not be a quit delay but something else, and > > what might it be? > > > On Apr 13, 3:38 am, "[EMAIL PROTECTED]" > > <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Anybody know why this doesn't work in QS? I'm guessing it's because > > > when you quit transmission it hangs and says 'quitting' for ~3-4 > > > seconds, and doesn't quit instantly, meaning QS tries to re-launch it > > > before it's even quit. > > > > Any ideas on how to fix this problem? > > > > Cheers
